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
- 09a3b840605d63cd253487770b465dd5cac0bf76c151f01081cb7cba9ba4d26f
- request
- 9eed16729299c36d7ec0821d696a080c6f4636b18b2b0242dc0eea2fc80c0785
- transaction
- 6288dc32d00223e419facb1cb5892947dd0acff97e80ae8f6240fa115441dd8dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48550
the chainentry 48550
- sealed to the entry before
- 19c4b5f02ab7c6defee5ccd656f04200602d27d2e0066e9256acc04ee333c4f4
- this leaf
- 760e55257f6e8089d17a6cad9cdeb8065f1ca42c27551358960203152c406d81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EE6dRWws2V2+2Y+A4l1YJ4tiOGPsleUiYQSeNJ+eArg76TkPAQaDW770/Z293QZTmai9gMCZC/vH3gdzkli3DQ==