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
- 1c56862c1c618cb2b4ce74e9d14d3f399b04aee8ea122c6ea1a02fed0f7a8fa5
- request
- e2b13ff0b49735033cedec2b4ae57e8823977032b14ab9bb14b3cc6224047500
- transaction
- 364fcd5853f695b9432d14bda8e869c582cc121c221fd75e710ff4504056c171computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40409
the chainentry 40409
- sealed to the entry before
- 8a756c6b0bfe185d6964f01d685050098184fef77ecbf40c2c4964b8d02ce267
- this leaf
- 59472af35cf2f11ac55d27e20d7a3e124e6f4f4231e017e0a2c2a5d4f477d303
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cr7QRoaF4Ilyp3m4TudHhzQpNJE9dGH4IxojixkfigN3BFnEHej4kaQ7BT0hJTDZUktSZb1jRUf3R650rSZHAA==