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
- 198d2dd453f05f3c105a8bd5b7bf9cf7ec06075557bbc8127925b1949c19a946
- request
- 1857f8fdb09cd3695f06426f27ab1e33834bd4133992cae8ac0f1f9a4417a49f
- transaction
- 22bb438b8dfb29aa2a94966ed7a82a6978ddff5bd778f361cd2b7291e6b983f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51150
the chainentry 51150
- sealed to the entry before
- fcef7b90fae94247d259f6c2c143369e4077badb1ccd540187d2422492bc5fc8
- this leaf
- 57e3f495a0245688664af2cdc19def877d9c28e41b82cfa6e3cc9717de2b61a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y1tQW9hB2K18l8Us0sPaTCEmMj7sU/72rKG3JtNfOWdVf2gGYpihXmr/wEbb+v9S7EERUu6ek07Nm34J3r1oDA==