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
- 830b7482d3c20bb3fa55daf3f746619333833edca2f045e1e4c47736e17fbc16
- request
- 7730fbe14fef0e8c963735394a932bacb16b4e6a2e17dfacb3590e666a0a3acf
- transaction
- 393832a07a08822c639013e259ff4ce18cc08f82ab3027dd05e30844b921402ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24028
the chainentry 24028
- sealed to the entry before
- 0370eb8fac078cf832bf86dbf80515fd1245b0fef51e844153cb4206c71e5147
- this leaf
- 7730b7ece7169db4b0080a903df507875ea60abec14d5dddb42031e569b701e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1FRZkLmjXpDZjDi6k8FgbyB/qwu/oH+qbaSCFirX8pEy7yB0SugjzAwq/cPAd4CplXh7gfi8zCZ/3gbqUJAdBg==