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
- a5bee62ca21839ab7c38dba9cc45ec7a5e1c39a82e3cc169572bc50927287f90
- request
- 563b6b5c707fb76ac2f237849d55fbb6b42882de58e51752cc6ee2657ed97774
- transaction
- 6f8de31a65ff0048f80ef563983c30e0e074fbbf64f71fc6379b7b937695396ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47612
the chainentry 47612
- sealed to the entry before
- 8c1025a41fa060e8410ef32e73fbb97e38dc907fb15c80821ee88fff89c6f228
- this leaf
- f065ea1119aec7b9930d8eb144989ac9fb7d2223436c7930033ed39c6b082df3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D+zzTJkH2DKviORNMaKhDAzXQbGCdPUyoNYNZXHUxcmlk8t172L3GUe8e4yqXq5WCrhjdFN3bx1s7rUXfPG4DQ==