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
- 6bf6973581e3ca8b5b696a75d6a25218c8b471afb788419780df8de88ebcd3ac
- request
- aeb6b052631b01a2c641e4b64f211d81ccdc32a20a345d7445007ed833e1fb41
- transaction
- 291a1e0ce85c91a624b8302c4af993f84c49b34b5a1897fd20414a391e10568fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59305
the chainentry 59305
- sealed to the entry before
- 6604c43271132b43f1b0178923f02052a420e3af831ead2fea0a4fa8a54bf914
- this leaf
- b5089a40500fba2b2ecfac8840c404cf2bfa70f06ee33b939782b6b7efd53b0c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E5+oR/PVmcUgg7ERoFpH2+cZVMG5hKKqi7BnJxxSlw9qkooG7THM5PLVdKXkWFCPxICsqrShgstgSOvDcrqKBA==