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
- 201f8bad5dcabd84fc17c6bf75cd6b5ab88a6be86da1eddade4c6c93f35bdedb
- request
- aa5ac92e0caa4643275ec5268caccc8b6403af8599bb58e9f83913aaf26d94a1
- transaction
- 0532deaca60eabefa113128ca8a4417e46a6a247e99e169d924f693870d369d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69321
the chainentry 69321
- sealed to the entry before
- f5a8f12cb9d21bb81da1267dd1fe986b773a9415581eb5be1e6e74d203517fec
- this leaf
- 31b5dcdb8d8be4402f8184755f444434cc6f310e04044e091da6631f097615df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EMLM9yPQ9h7TTYqOXe73Zh8TQc30JM2Fcq/HmjaE/1400kUfKDKgy0sQb9wbeElhj1MBfDiwobI8LwZ/Jg/pBA==