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
- cc5b2c8d6d2531cb1367d820bbb45cdf48d2668788ccad2df7b03d6ae140b41c
- request
- e5bff08e603a056b4358b684a61bd3a780f25936471bb25909ba0a775fcedf83
- transaction
- 026ec5b40071fa0db25c8d0e6e7c9750cc9496f317fd655e28b350b2011680a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70460
the chainentry 70460
- sealed to the entry before
- c200bda5f46f87995d1b475b9637fffaf68f336248289926b024311e51f6e2a7
- this leaf
- e58ae9886cb20f47a63597dc4d2e6bff4ff1121833d812973be4061eabfb230f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kg05+d0Pc+vcOCOMxcZn+Lb/1c+8aPACuJZiPRBt4fZ649zU0vWTuVvV08UgcCNRUeSFyYLgV0lIdrRmiGxJBA==