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
- 8d630a17b4858332c76490437b7302b04a3a1d4c917c5b471c879da78f7a65e5
- request
- b178ae7650b4a1e52dca418103431d9c4131820d034249aab0fcec8de5410613
- transaction
- 5d04135a273749022d076c3ed595258929ff235d6ee74493b5c477d466f7ccf5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69442
the chainentry 69442
- sealed to the entry before
- 86d4a99663434d57aae06b07d8a057859a888d120fd087835d7dde87ef1a60a0
- this leaf
- dc23e250c05778e9e32b0e230ce93d93313f990050206c30dbc12ebb37e73bf7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SclyWruONl1fH1EVKrjL8k4wzSUptatKSgs85hnpNMh1t4ubYKYCmdJnUn2SqVcj+doRGUsMKmMsat1+UPgZDw==