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
- e227a7829146c822e67179d32bd2aa170260b51b05399cbf33a35f0313982150
- request
- f4b0902d21f000f33270271527d0fe41afd14205882322bcb291f16814461a7f
- transaction
- 0d54cad8937255d9594a3e436ebda7ea32866565cc7149eb9ba86467625b4e11computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64097
the chainentry 64097
- sealed to the entry before
- e8c7153a0875c6cc2fd2de46d21fc3125226eb47ea840a71bd3587522233ba09
- this leaf
- 59cc5d1fdc21ee5278c325ad488f612f9953dbf5e5e5b9b3add3952e30f03b9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rRDrqd1ykB64hnuh9k6nx1QDLSvHb49vLX3g/LIiFPWDkJEAxT8haHt0mluGXZo5H/rf1zqV5Uqf+oRnzxSWCQ==