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
- b9536d305a27319d5cc6230bbfec12aa4497f58fafdb380dfc929f336750589b
- request
- aba1edf878186f097c4468bf76416fcc7e43cfc5fa9b16e63ce0b90d088a2423
- transaction
- 0e2c7d4a5ce8b7ccd302a8470a461f37b710edc176b871af723cfbd6e242212bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31288
the chainentry 31288
- sealed to the entry before
- 57a976d4dc386fec69fc491c952fb48741d24bee62d66c67662212e3b18deea7
- this leaf
- 7f682872739116018a35c0c500ed5fd10a56dc7f6163ca21b41929fb0c820763
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1V4mcF2WaFUNjJtFyA0CpEkX8DZet8PT/NKp7nMxPQwngWANM4yOdPhjHRDzap2pdd4dW1GkyYkj928g58ZeCQ==