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
- a6cb300f28d06192135d0a09327a71f539d51f8a9ac8714176e3284d6c375b15
- request
- ce07c7e95134c87d9cf1e8181d5f990cd668fa483a7fde3d4d414358138966fd
- transaction
- a6466c57cdde24639345ab785f8391ca6cf3776282f3073b5d1c5cf016e373e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54195
the chainentry 54195
- sealed to the entry before
- c76f62c6a1478b1e39a0c5e0718ea89a4c749ccc7b62aafb009c21cd2c7e0482
- this leaf
- a51a06db53aa1643153ef3614be755d18f56a431531ca64f80cbc89200df9702
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VhIVyHmeoQLVavgRb8c0VPKNFdMuTRH8N1IXkQO2zLhUkE5kT5od9ynApuv2dlDdwMjZYnETQND0/l/1ek+UAw==