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
- 98ce3077da68717cbd7ae6debdc8065c670752ecaed7f4b894a82d45b97969b5
- request
- 9683e4e5c9ffc988cdb352d9b89ab923050e958afd1c82d68d81a404d09ca585
- transaction
- 227845967d5117c1b6ea1a3338164a62f1fae7f84dffc30c8a51af067da0ca4bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70983
the chainentry 70983
- sealed to the entry before
- 8f23f89dbaf2d03afb512dc2fc717ec69e84befaab0d4f1d6657bfb1697f82f8
- this leaf
- 9257359877ee9f42a57fa5d33c062e8f6d94fe2571f345111d780e1ef9145fb8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ck8lnS3syaxYk9R61h8lMnfKHBlYe+6palBABSvbmQd6XFnlYD3rp52kTQ2IvUdHrs8W6vEKpdh+7ysZpDNgDw==