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
- c201a3419be81029f294b99b6a13a3f45cb4a71d388f4dcbc58f713222f37075
- request
- 851e83c163547515ccb50e2918c4afbac80289347822584bbf211ce3c12ec804
- transaction
- dac94116b9f04ed7ae0aede2174ce4cf97f65a854ca7ef075e7bd2cb0a72c7c8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62817
the chainentry 62817
- sealed to the entry before
- f830217e0a69039c1cd741ea783eea6e7c479b289b3634fac3c640c691b596af
- this leaf
- 20dbc56e389e1c00284d385ce90525609a2eed393521817572e42747b9179765
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DWYV5w0UgYm/5fRw21Q7AGKRo8zU667jq9j/nW/a5djbLjspHWsv6Na2acPPZ8nfSOZB9juZGBUmFe/aW7KnBA==