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
- b32475e5e210a19b499dec55af9d779906fa1865ca1e0eac94bd03b30b693775
- request
- f9e8fd38d1641ec831cbb160c052e83b2a624b17cfc95a84bbaba5c566cbfe95
- transaction
- de6169028c6b79a19d863f6ee7f5d0353c890f3bdcbb09e13d09ac67bace0e16computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73569
the chainentry 73569
- sealed to the entry before
- 3f1c0e1ecfe0b2948291004b78a22aac649831bb67a7b6eefb99ae424d4196f4
- this leaf
- 31ab64f36f486f0c6f2ae6c23aeaf10832015ac84865f97f78725ecb70447631
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JkOnpRfEusLwImw59QomvZw6OCCkH6/z/pO6Khnac5TRxJlkBci5W5s9esD8HPMxlCxrtKa4DKInkvVNfKs/Cw==