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
- 77b43498ae3bfc04e514728f54901899721abd85a8f771baa5171619f6d4a783
- request
- cf71ad94cb476ff6cbba15ef8e13eb3ab45edb63dc2390bbf41625808046a25e
- transaction
- 3f7a59f45c4d51f3108720ffcafa73d45efdabf5328691bf4b3bcca344c2fb37computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53111
the chainentry 53111
- sealed to the entry before
- bef1cf6062729568711f478baa891402f4c638ebcca4491a8d91fc84bbbe39d0
- this leaf
- 7fc6379a536fa47ca89de41b23255267fc8aa0e8d2d863db91036dea0ac8e561
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LKyoBBfm9gvwPL4cgewLpVDB3UGgqda71U16cUMfzZLGjSPf3eUxrVC+hHdA57+fcrvIcyG9JCifT8g3kWhsAg==