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
- 1d67eee3ea14a05fa57325da1d70454e125825a85045eba3b9546e51473e7ce8
- request
- 72d25d13bbc51d846d559243673c947cb128fa1d71b7f12ca16039f21049f162
- transaction
- 568e429da6a73467e9d6477d1920679d35937c7f76e1e3226c0d6113529fbe19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20787
the chainentry 20787
- sealed to the entry before
- 163b6cf6fc9eaee878e59247f1e4cf05ea8947c0d42546dc679b96fdc46f1fe5
- this leaf
- 76cd09623ca811706e599b37945df0b7aeee619f419637464689d34289650d48
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Mt3R7vOG54BbnlkmJ2hT5EU38hhCREpBWwc8WUKbYVK/dhoxqJOCp1cohT2IGZT7YpndPae5x59MbZfVblsMBg==