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
- e649fd5c4339c1c24c47f5984e99e6b94bf4b5f62c4388775ce44d07458472e6
- request
- 4e12d43e33eea69e4ac5372a42a56beb5ccb6ce8dafb2b231461fb2997d126a5
- transaction
- 0c731e566dd57eae207e1fcd20f27fb2073ace3edb658d75fc96ef8e5ddc7e4fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69112
the chainentry 69112
- sealed to the entry before
- e9e7f090a7e9ace8ffc4e63a6626fdd70f8dd1c9f47c3c695a63cdb5dc24164d
- this leaf
- 71e28cfac59ef2c574ce8b2689a133db9fa3c9db62d9dab155fd45ba17847c4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MGhA7on3TSQ1Srr3r+d/tnvWa2TU+JTUmFXo6VGZXSU4cIP3fChatQ+oh6razMvWVgyrqNBvlz0F+AxLRf1JCQ==