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
- ee89a09c2a504400fbb85af362a71d4ed903a3044c2000f8d7e6440db751befb
- request
- 93416511389370bef4013b25ffe16c87936b91d7d90baf92d216de74e59cece1
- transaction
- f05b1fdbf7299f3a0768559d1154b96093b98d1713fa649620612617a0194ad3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15885
the chainentry 15885
- sealed to the entry before
- 18d7755d2f2ed135e1a698a0fe25393240cb190525297506fd2ed4a0a2fa4b22
- this leaf
- 3e35fabadb002077847f0372ef2e3bd99e1ba5c4165890f567f1a69c91739e94
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /a56F8R1r7l1pQ1k5i+iysMUO1InxKx4i3IhaCBD3pc0ZGoVGeXI2MC5nsi6KAMsmwFAwpVD/rO/NzYxrkH0Cg==