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
- 6993fe422a8e1880546d15363743e9401f21c2c86c2bbf0d572824d938cbb35c
- request
- 0f3f165649d17b8d24ba73671d74af0eeb6c9b34b7b70d445361ff364891d0bb
- transaction
- e5372c20b2f01db0e5b7489f905e9e11754e09ad71e11b145ef493696792e971computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21223
the chainentry 21223
- sealed to the entry before
- a6e3f6af7b28544b8f8f00938b8547f21d7734df066bcdb3820b37b82b131523
- this leaf
- 543826b9e23265d6419fc9e0af7c0e9a4977d02eb23e953c6b1238ef1c7ac424
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7rIGJMgLpGIOed+hQDB3ECEB8WhtNWKIG/4dNnrQuFB+/+3IvCl7EFPLqAfmhCm6dkZLxqzS5L1hqUghXI8XDw==