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
- b1fc4f891afdd3a455e2cc33861041ef709ed0bbb2386bb91f0efca451dad46f
- request
- 0049aa5f3b4f679f02c4d016558261b56bfcadea287f80600cda027f77cfbe8b
- transaction
- be0c7897f9edc8b02a06981f6905a81c1398274214c631edf48cb56eef0ae38ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17121
the chainentry 17121
- sealed to the entry before
- e4a3c1f6be925f44f693640f5a37fa468e5daaa797ae8086dfa4f4a2610b2599
- this leaf
- 9dab61b7c9d868bdbe4a937b87235e2956e74983a9413787b790cdfaf11151cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FP4/CxUf0yx1h4RP+rQX04b0IhcflRgfsDR502u3chMtf/n1CyPabuBUD2OqlQf70lSRsJ2cXPjHKhxst4yqBw==