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
- e9067fce228c040cfa5afcf2eddff2a4aa43956314c406bb83b07f0e59a65c0a
- request
- ba8a8eefa7a4e2866c82b1582f46e98fe5a587b1633dbdea984a4242197b5cba
- transaction
- 5ca5b14bbbfa3bf8e420061e46a4dee42528371e347aed8b6a23e8786b9bff80computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48229
the chainentry 48229
- sealed to the entry before
- 999c486184923faa81ae3ccbbd1d85e49b8a08d25f7235c617d1a2aa79b502b9
- this leaf
- 3e81b0a53a3a83e28c6f0e16a70a48e67ba0cf4642b8d9a4db91d545675bad96
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0F9l85x2NeZei1OFZm564HCYCMR7czcF8gbjV9GHSLaRV/OWpZEZY5v1l/AUDNY2C7U+YbdNzhOzdFHW2ZkbCw==