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
- c35d27946eccf8863ac4d0bf414fd040992de72133ff9b27cbe23b1c9df0e287
- request
- 5db985022cb47378682039764b9654302dc738e3176994f1999ce72797392917
- transaction
- c69bd0d1b29d68fb34ceb297184fbc67032e8447a0df7091200b8c7faabf8459computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49305
the chainentry 49305
- sealed to the entry before
- 2bdd6756f415b4303354c27f2b2d4d7f0d13ffdd4077211386e12b5e0cf3d026
- this leaf
- d1155644fd131abf4b9e9aa0136807aab97ac0754af80c4cec8015a3e350d6ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e0d5BpgDJYAnpLI5u+v1tooZe+Wgz1gcIA74TErmic1pFjN+XxvpSRgVaosTgqDkoDy349fM/s4VZG5LJ8YwCg==