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
- 92309a430fe840f1db43b3f7d80f35beb74e8714bf530fab03a7c27e9eea9fdb
- request
- 43304fdd24f05616db63baf490481841165083d0802b64eb10dd0ed46469c057
- transaction
- 20e1e64b4acfcc2e39e1073545fcb2a7e043309eca8dd0c3a085db885fe4d2f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8951
the chainentry 8951
- sealed to the entry before
- 4f5bb798705845f3295d431b48a8d4f86c0b020bd33a9db621332fa02143032d
- this leaf
- 34eae1ee69e9b51a8aee60b9e29c7259e3021b97dbcc742581e60ad23abbaf0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LYhgpE7OhQbeiaQFFByAOjZQSXn5Y7qdP8nxzDfdpH3h/tNI/gMvXmqBJXWXdHtZYzz0ndCvetuCwo80RhdWBA==