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
- 34952ed983bce094853f31e81fc53e9dd51e71c241efd9ef6a012c6a0e482090
- request
- 45fa82a5724d9f1bfef24e513386c5acdc16da267be55306c1ecdebbe47f288f
- transaction
- d3325e809977f01d9f19d3ba88b5bab4ac690645262f78e6c18d7de5b86cf362computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38632
the chainentry 38632
- sealed to the entry before
- 6b87114e577bb645cdb2e028f60e909936f9b63a6e914cea7f3099b502b85a1f
- this leaf
- e897ecce584c713e9424c1ed77875e5f9acc2bc7eed52034b65e44262e20a51d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ehyRxRMSPpEu8xOhaP9Xu0yTCQE3F0jchX938jaKNExlXUbE9T0BAL/PyxeThUtO+4DM99R06wZOIr8C+ROaBQ==