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
- 5db7a26135fa9c46da07f90a5a20555badacdf49485ac051982993b0732744a9
- request
- a17ba66a0401207ce385718ef4f826bcbb39c36e3a6aea61b507fa75bd890eef
- transaction
- eddf3ab62abb00b81e33637e13ae0ecad059b558b2fd8884b4180646e8b0d16bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9929
the chainentry 9929
- sealed to the entry before
- 52cb23cc0276891036ebb8da19a17574a05c8abe33b7c4bdc1271c04223cfae1
- this leaf
- 70113d23b03ab3a157255852b0a14ef568a6ba1e4cade1745a9c58023f565048
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A7GMg7IV9D8EOVuswAUp4IsjK2YlzvVN8qcOctXhhC4pHJLdmAebRY75eZYVuarooqgCyyWq34e0oNkR+h+pDA==