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
- e427f15238102e94ad94476d7e868c2901fc515c9b5b90f71b5872221ee96258
- request
- 47a5fcd3b8ec8d33a5ada655e7fd47da02827802071593e9273fe000fd3949bd
- transaction
- 1407aee2392a3feecc4ccff1802d1a464ea045e0a2ade0868e1fb6658240493fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45538
the chainentry 45538
- sealed to the entry before
- 7efe529a957410731dad395ac7b3f683d568d70dc54aa41881e294d9f3e4b17e
- this leaf
- f14e10a84c45a7d036708f8b37745f307bc25cd98a6711054c98cbecdd39b0cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TFOsmldILXNmcIzO1g+/v1rR20DfAr2DZnQMSdwzB41+P61+Hkf+6YuBQLNrKTGkOkeoGjH9tAWdpq35yMd5AA==