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
- ce22ccfc96859c3e81d59e5c2c980ecda83d6ddefc48d6a42f0bb3f8a4a64283
- request
- 85e5acc65111e578bc467d5f952a44330ffaf4db6b1bffed9fde4fe774e587f7
- transaction
- 1bcfc4c060459ba171b9dfcd316a70f75bcbe6b33132ed86c4437f0f15c54967computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51922
the chainentry 51922
- sealed to the entry before
- 21bbe5478c3861097edf868efc9dc66de75b20beabd2ed0bb334735d407240f3
- this leaf
- 5bae0da77a75c56bdc2c1771ce9b2430a82d5c2eb22c3000e8d02cfe39b06f88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JoYSNMrCfw9rSF8dhmnO5MIOch/G3K7nsbCiMrZ3Ic5qn0kDIlYIvLQL3jDirK69Yp8kvpl6/SI4PIWUkQLaCA==