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
- 2c2ed93685cee4e4fccf8a46c33ea580ff6dbfd6ff645cf7b42b7f791843a33b
- request
- 1bc6901344b5592a11fecbf7433c69fc7466667a85c89ef642b338db2889ff93
- transaction
- 9fdb7dec9f106a8a74222c978968479e9324ae5aba36669d97869c234c44b93ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63166
the chainentry 63166
- sealed to the entry before
- 30f403b43b790ae540d064daf9965bde16a1d284caf5b708d5396df38b475f55
- this leaf
- 659b89a170c2bdd756cba46c12bb4f2f64b018ff7a3a82aacf040dc8204188a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nh2uktslOoUAxY5cDYDn8WD9uHwgsiTYEm+qwzcTN/4d1W2YuqI35qHaEBDzu+QorFN893vgRZX+2sEI8ifZDg==