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
- f5e0633c44892faaab2ebc9d8cd4fa950ef08c9269aebea161d6012cf37406e1
- request
- 5c871c68fbef68fa39eb8f56e9d71f0f59d83d0c87a3b32e8684ecadae5f287f
- transaction
- 3d4b93bdeabb5f77e93b30ed6602d966879853547f7d179af94f0d14ebda2f8ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42193
the chainentry 42193
- sealed to the entry before
- 4f69d860f14c74714d0bdd68b08b4c4e6a177372798852c2500db7b9cb1813c5
- this leaf
- 6cdf658a9c590f6dfbaee90a62146401281f796d4dde7e944cbc94e6158e079f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VgLBAzVXtvHwabtBlgcm3zMTRH1+CJGW/qBFtHHsq1nfbr+IXpDcNA5GWzMGigwEIzNzS2imjFvawOliRRU7CA==