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
- 7b13a8fc86e7b5938d3735cfb73456a00cecf87ef9ae5abee5d73aad0c79787f
- request
- 1cd7734530a67b8318795d60c9355d462ec3178e3fd9959e7c1607bcb9679fe1
- transaction
- 71905c9d70498b8e30f433b96e09a4ffaa7fece24ac13f502e16ec69c5c62823computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 221
the chainentry 221
- sealed to the entry before
- 26f66871c23cebbf9fe78963925473a255d53ecbded17a114464eba9be546697
- this leaf
- dd22a880189091277419e24a75c75d7bd530123b5e516871c182b6aa1e019ec3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SLkMi9ibGD4fu1xTAbD1ZkOipIZ87WHJSXFYmOxxmZcpKZ/TUEL4SdZ4GmDt5CAwY3fqAjAOF3IIIqeJyTDdBg==