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
- a85fbe9156e76fb8c5f309435e875671413a9d022a00def86f6e8cc2dfeb5e84
- request
- 44774ccd8cee9901e7a2b9ea754dab854af5045cf9e72073c4e24133f459585d
- transaction
- 8ddf64418e40cc8054c0841da767e520ae2ec5bebc59e0fffbfa18eba16aaaa1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3594
the chainentry 3594
- sealed to the entry before
- 11e9bdfea660c3672c20f07da98cf26fd44fbcd1788c6c30e95f98ef57d480c8
- this leaf
- 41c8a2fbd156d9577b0f14f6d6ea34a0a78fbdb13d98a399bc96aefff58755ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UMqYvx1smlG0a1M8wanzTxE5mu2CzsH99Ua2JQAYz80E8Ltbac5jIkMrYEggH7+GlVOWLt93s8rRgc6C6JsLDg==