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
- 2dd9699652a0edb10967f5ceb2ce1b2ec96c2d66683d1587bcfc738fcd1a86ba
- request
- e001f762559e36431e7a6429c88b0c781a995829943e17d2c002e608cfc89dec
- transaction
- 222d7b98b3023a65c9aa6657a8558ba5278172e2cd18010b6a49f2b39bfc5deecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1340
the chainentry 1340
- sealed to the entry before
- 1600215cf621b921d7f183e7745007c4d1df1bb6dbf0efe432bdd526cd423ff4
- this leaf
- c82281e7e488ed0d9b512ceec85ad53ca1dabaa8f02b61dfc880df67795d6a11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QAcNzRpOuDYQNekAYXNCAmkL7jvZEUAevwCht+uRHd0Kdr4N0KjDwSdOgYjdArIpekLAX7AmVYcjsuVC8S/zCA==