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
- d8db708bf04fc244dc850667a87e9da8eb66818fedc89164d282d73b3faeafe4
- request
- 4eccd51c672deddd3dd3f38f04c894b9ffd276ca76dab8455f57d94ad1134879
- transaction
- 616fab8b06efdfabecc50aaf21abf7407e91ea49cc7d6ba46164a56a75698b91computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34838
the chainentry 34838
- sealed to the entry before
- e37a38f63825776b43619e87ad188051b2f94480b78dd767c7f6dc608489d8d2
- this leaf
- 06df396f4180980b7282cdf8cdb6b2eb32518b84b1864e49411c57bc243673fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4HnCJZBDR4I1vmK20AjmvDBp3VDCyJ3ZkTGuYQjAC8kXUA0gyXxqr4rnD98+vFlezUi/pEDqy3g94OOxNZr6BA==