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
- cfa50114f26f40829cccc6d7e0d050fa774a306ead884d8400b17a720e21083e
- request
- e734d8da959e4811e73f9a9982c60df444e1a94b71cae5d19917c440434e6297
- transaction
- 18d7e8990c3e83e72afd48c98ea38a4fb61263f98398184fc055327648971674computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62186
the chainentry 62186
- sealed to the entry before
- b568a17ae308d743d6a7246a2bd3fb28ff7d3c5e959c7602727a28aeebdd1723
- this leaf
- 1a95b880c15b608d06d14d24fd839ac6d387b72aea6b86f760a2b21dabf3a60c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1Xt0WPSK6FUbmM8oEVwaXqzNprkaKW/LsK5/i0rV4MdiPf1KTshpR53/NJ4NvNjCbJbs/Un+Apn4VcJ4s8tEBg==