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
- 7adcd5e11da6e9464a15e9022e7092801002ffdd60d8d49bc5e77c89d9f12d30
- request
- 90ad1db9d48d709d5f0cc5dc4391f3abac2b788215dcb15f0593c114dafd40ce
- transaction
- f87f49028743f72be941ba36a754a71ebc90340574b5196a30f8f42569535468computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39859
the chainentry 39859
- sealed to the entry before
- c883359a3a493b28803dd1c8c6417f665b7be28596c24400d8872f40d7bc805d
- this leaf
- c7a4a9216b1e55467e90951616ae3345b4ed9cc3da9e2e80b35c2db7fb820d1b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u6sqcLAKKFop84fB1ZEkbh2Bd9SG6bkGm5DJrfDDK+gUCocxJiiuS9b02h6yuD81hdjQZ5jfynLVz26HgYPCAQ==