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
- a5bfe65038ecfc22551b27d91b1ad1a1ba3de47b4fe44f4326dc1934e0b86569
- request
- 10b128ad6d54bab034b85f6f3be5632bcd6ef95e90a106f063b25216de1de816
- transaction
- be8bc18e1a9fed416ad5e58aa595e09fb8c546eca6bfe59949848121decb9ae1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29642
the chainentry 29642
- sealed to the entry before
- 6ef969183e8a6c25576460ce0c16b7fe71ea377469c7265968d4d0510882a1ac
- this leaf
- 9793167f4c10c2586c2958e7f366651b57eec2bb97859d5ce70fe97eb7afb003
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ca8YjCfqq/NRkki4a1unlM0Wr9GDCPlPwcTPzN6bQhDpEOwR7St5BrFFgVEkOUqdDxbSVP49gO+lC3lHvgLeBQ==