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
- bdc13fc1c51a7a42d71f596504c05a7be62fe574e12eb6a2752d7dfc4be84887
- request
- 40634738471bdeb12f91c80d28f3948ae865a98b72ca2437fc837266522bcbf0
- transaction
- 805230f2e9297f973b6bc59a9ce1335991c247584347ddb86c973b36a5f2e2b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27442
the chainentry 27442
- sealed to the entry before
- 0d6809452c938a2e280a2fa840d8d51d58c13396baa9f50012c5c804ff003a12
- this leaf
- 969ab493e00ce76cb18f5385931c5848a8c105607e9c968a9b67fe299917331a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u6DcjnPndL4GfLXjVPW/6wFKFXLxVbEmvxRBkxfozh+l1udUE1FjvvKjpgEvSuRz5PnwuTgWGigLEfL5RZcVBA==