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
- e8dc9735a65317b46a11043ee684a910741490d754397d644699c1f7c076f637
- request
- a71b5efe29ab83493669c3f40c5990a99f8949c65dd39d2a8bed7d7d9d3029fc
- transaction
- 8da894119522f5bf621c490b45af7b38934a28b4e98d583ef84d0f7ea94a862acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77154
the chainentry 77154
- sealed to the entry before
- f499223810c6543849152eb5a4b71d538fa80ebb9187595996a9e9527cc710be
- this leaf
- 787ad9e7489c3ee31e86435d4dc8d24087a7b8a31b0085c72f18705247eb8591
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- So4Aq6FsbPouP7XSwlk5nULmmFyip0Y4bDvnYPsREG9lvvEFctAFQYFjRzqmWmku90JGHSEgoZiCh7o7mAhFAQ==