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
- 2b4b0e0e46188ddde578f652829fc1b2e87ebafacbed67d04140720ecbb27bdd
- request
- 664da8884521fe0a1a7299e69165677056327ae4bcc9e62ca425e5bcfde91871
- transaction
- cd1c4a3d942aa6f46e5ec61c70851032a102af1ae35c1233e8928eafe8d3a9bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37608
the chainentry 37608
- sealed to the entry before
- 1a6be62aa54b8ac93e6c12bda2a4c4512490ec96dd1bec4f9182f974b6503064
- this leaf
- 697cae4764ff21acb09272083703be49fcd70b726c7835274ce8a72fb65c5912
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OH9ogmh0SUXCI7sknmbYHCAgApa6ZpD75vF/UAre3grwQxe1lgWtqAvebOD3qvQQxsqb2HT+eleYN5oX/tuLCw==