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
- d1512a376713f7a7286873b9f318151b81341a196a9b89a169ab24b486ce333a
- request
- 33e85272950b15576c88bf2d99545672e2ff64abb467faa6a378c8a097fbb029
- transaction
- 83dc3e2d3a45be46d31de59221332bdd30466bf5a2a3da290f7bd090fcac0682computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41395
the chainentry 41395
- sealed to the entry before
- 6ca1763427e9f21a00847a4d8b1eacb24a0fc841b27bdf85cdabdaf3f20c43c7
- this leaf
- 2fb2cb07556f952bb29c2677ad4aafd51f33b26d85de3282860bb3874ac5b3df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Uh3RG3ZlLXVlSgeORafyXdOxIsALOL6S+eLd1E/GIVNsHeZL4Pnw/cbpHCJAHJrYQrql//KZGfGUqvvkkC0/CA==