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
- e942ccaeaf8add2d6d459300f753d21a1afaa8acef10e2ff11c4b294baa05b17
- request
- bdffac7fc9d771eb106946ca351fe7c0b63f8012144c56d11451eb218e4ab8f6
- transaction
- e13fb181c04a60fd5c7e34d60eb3cb9e1c1ea19b4a08b7e7dcbef8ae394a08efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48112
the chainentry 48112
- sealed to the entry before
- 6009d0e99eb479878eb440d79b18f39f06511002504094b33703e0e09be34a1b
- this leaf
- f1d66bf79c720323173df806bdf393c58816843876d6cc77b81d4e80221c010c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GfVLS6kMQD/zxQKQiDFsYsOOCwSHzihVf81QY2+hRnfNDl70w5Aa0bSeve4hscI7Y59QzhDAg8Hhu+2tlAE0Cg==