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
- 945c6cf5a52d2e7b51ace1e8ac0430af2652e04a05fa26de89292641fc20952f
- request
- cfdffc6146797778d73cb3bd08c985438c433293ee68bc968ac83a2303c3a663
- transaction
- 59729717671f3096cc3b307247e6d45bb4903427dfcd1078d2a82e6241e17450computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63900
the chainentry 63900
- sealed to the entry before
- 45fcca39265f01e3c062fab1eb80a5d4e24f5ef21c950395a4a9e4c79e672036
- this leaf
- 2c0ba92b4890ce794241572e05300d95b4de8ac91730aeb6ecc67e32ee0dfd53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gm9Q+6GIuPRR2/iIPd5q4aXZhfWmtyrawTukyO4nfN8MHAdKndBlHumRN4k/wOEC45Bnqavi9NEwGkHDIcGzCg==