why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 09194e14f1613457ec2b2c5a8f589f9cdab4b92c7462391aee91519810cd0033
- request
- de01f123ed19830fc50979368eb520794a24ce07ba8244e87e28591d391ac8c9
- transaction
- c3eadc631a8bb9f7cf55ee90f3c89efa2d283db971690ca8a2fa4aa144b97b2bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38123
the chainentry 38123
- sealed to the entry before
- a1ea1ae5ffdef6fbcdc46db80a27fbac6fab40258bafb71522c01ac27e8db7be
- this leaf
- 55150e9000e4a68d2fde61b549cc272165648aa39ca2d0f92cfdb8f1d3305f56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Do4oAGs/h1c9DgMDFzaf6YpmfKkLZMKZ2XNyOCDVyManWMe3KoqaCxK77tB+rcjq0FMRjVmDAI3203dQT534CA==