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
- fb6c88575e562f019ce9138809bdd86a42ee707e0f4783b41621d847548de4cc
- request
- 4064229b4d1e19f5b4883906a287752cacbf170ff2044f41e8c0c1b716cb7403
- transaction
- 0bf68a8a53e2e64fcfe1e7693aee2470c009c2be76b21acfc4252f2a07c79a6bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44528
the chainentry 44528
- sealed to the entry before
- 759b0925d5ec2b95432106304511256f97973a404666aeed5e46458c63f8a024
- this leaf
- ab11faf3ecb5f0bad55690c0065e9193978959608cc93ce3d978fba64ae81f9b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FiKuODmSGyPcpx1xJ5vFnXlwfZbkSdJVOTj+d8mmsu4/EyYvLprtF/Am2p+/LglskGm+JIgcyeldzQTAa8RHBw==