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
- 66608e05a203b353053b612a65a034cacd25920bc23647598fee8de81b79a397
- request
- 39bd931403efd0f6ae648250c238d70a33cee3f5a07aed0c6d0ca14172da86e8
- transaction
- 1b5030d8bdf44018db2f26d3ebbb824bddf016c3dce993210a86ed1569a38cf0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64920
the chainentry 64920
- sealed to the entry before
- 550e7a4b4e0174e2692d20ec2041d5890c4a70dafaa7b6ecb4c0ead8fd7ae6e9
- this leaf
- 88a08bcadccff7e383a29fca1f743b75eca589bf37556e52b97b639b80543c34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BFjU5OYfvemi677XCR/Wj6wZCJQYFxXq2/b8n1S+a6FfhRHshw06I28Fau8+2rtyb9q0DQdenDW+s8T4RmmKCA==