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
- d80d8808025888d63190b667fa63f72f7f179b3e65f0c9ef5ed82a2d0ba79d5d
- request
- 8f29d4ab0b54ea3923786a92ca4414404856a3a442cad1a8590335cbc9f73e52
- transaction
- 4f4f1fdb00e82d65afb78be9bcde995745580b297676cf2766f82e39745c5effcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59503
the chainentry 59503
- sealed to the entry before
- cd462ce33e353e45c7c1f9619db41252382c95eaf2be2704ff3f9c624572df11
- this leaf
- e9abea591debaa77b79b573cc6e0ceddcf61a72fce65718b9815144c78cde345
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iQc7kjw1qhQC1XWpoN5eaXi5JPTb3ELzFlYZcwVzNX7ndcORRsrER7Cs9sPNgc2HzCw0jsuDBWGUt/qTuZKLAg==