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
- 40f24bdf2772c3a35690bca8be6f2444684374c6c4ba991e291651388a8768e9
- request
- dd48b75d92440052e23a7851d900700cdf5e2d4ccc234cf68e62363c9aa4431c
- transaction
- 64834cc17593bdb125c13585074510f68dbd8dadf6ee47d6136a7e8b9ffda2c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37718
the chainentry 37718
- sealed to the entry before
- 93f4e25bab8a36bb8e84a53ac1c38dbbcadba40b87180a3d68889307b2defdb3
- this leaf
- 4f3a0b0bcf008579eaf4e83036489cbb4e1b31a180142dcef81081e5631b9f1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9t9mrn679g52pTFjz7rePsQSfApM2ZUchU2fm2glRPtGyHI/YlgFCia1i5exUyXbaDooJxNRi728rKo6wbllAw==