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
- b9b5f1ceb3648e9859136dc6fef0179920435e3dfe1e7c464eefac68d071ddb3
- request
- 427738ec822b6c260a9fc6bd3c9e3e805e8a9173f214d391ae4dd1e30a089d6c
- transaction
- f2eb0b8b285849f10f8ffed95111920df3432476a19f54d2013755034cde3477computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8546
the chainentry 8546
- sealed to the entry before
- 40ddb895bdda4e186777773d2217edc973cb255b1a7cf7dfa0ec5f35b604b1b0
- this leaf
- 9924543db90d5333e7d5afd144077af55b42b1697dcddcbcdeb8596d80e40322
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AmheHuTKrOOXxa6sqiyFZT/BpfaZHsNSF2v5F4vZB/KTOX7Huviz4WXb8TJtPo6G7uJEpZW3btMHQB+RHsREDw==