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
- bded52905671084159baa1e900120d6b6fc588dfa0a2aafaab72fd2ceb4e8d5e
- request
- 60cea007a5e49bc7f568c0fbc55b1aed7fc80187528e1cf50bf495e9c11bc06c
- transaction
- bcca0b9c07489cd3cfd74827551ad5a5ed54e2c360dc35dbae15d0356bb43753computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32336
the chainentry 32336
- sealed to the entry before
- 152faf16848da02d28fb7c3672dbefbc4ea5eb09ea8b5e2b5bb38b4c93b348c3
- this leaf
- 6445357056a29cd4440ee2bd83f884d1b5bc7acb9b903babe9b3e69b25a7fa24
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Zf5xsUPBL9G1FLe2kUoxSnm+UkJ7AvY8b+bx3sBrvxWRVtKSX8vwhP2Mxw5lwHH+GA2LFb3IHd6EBZJKzFBZAA==