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
- bf3886cc0a9e2744cafbaa17b13334b1d043ea9988d1e919621e0575385befe4
- request
- da16e22e9ed25e3767df624a6a27d1561906b135d1afbd1393256679f59c3278
- transaction
- ba72327e021893ec21f6707abadcaa4037199e707798b61ee2362dc4473e39c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19487
the chainentry 19487
- sealed to the entry before
- 1d05c8e4fa8135431a14c52f1acba4a4d586a73b93249e9ed2c6d4f0369a8ed1
- this leaf
- c77dafba3cb410df656c7f029ff3780aa8fbadc45d6780c587125601a97a4c9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z2aCdl7AEHRPlZ0b8bNyHCB89JvBcZevd4IT6u5M7tu1GUCuGME9gDKRRc8+5ai/AhMQ7s8ta1OPhgHrf5mqAA==