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
- eb3cac6ea599ce08c5aff8107718387949e8d9892e30d0cd3fa7a7dcb5b15c6e
- request
- 2e9027b7996c6960623bfdc67b1f42388d60c61ddc7fbf1584dc48d31cf54e55
- transaction
- 58ae34546a69466e87124b4458a7a63b764a2218c53033e46a5a4895559928a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56458
the chainentry 56458
- sealed to the entry before
- cd3ed7753dfed90b8b04a6ebfde9a6eaf69b3e6e015b3cba5e229d74f20ab700
- this leaf
- 7c9707a72d8057183c4c04c155182c97afee5d93537dd707b1d35d4d014ac0d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GVWvCYveoxh4BwciP/zm0ma94zOzdOJOeAvxz8gbFuWMKVNGYIzTJhXW3hsBrmIiW1+TDrsH93NULZjJjwodDw==