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
- c76df30576ec5d8f3693a55116597741729f194e33bb134a23bfa1b046c92e7e
- request
- cc2ba74ddec68a08ef767d4c3867dc89eed394fd01a2493df7be3ca72388c799
- transaction
- a8838c787ae36363b62cda2cc0140c870861bcbfea0640b6525c0278f9b10853computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7030
the chainentry 7030
- sealed to the entry before
- be340cf77facc640270f562fbf038a64f8a51f2b5e2b4452ebba0a1a4e7b9332
- this leaf
- ff60f80ac5056e4fdf5e48ff559a99f11845c825a4ebe4153cebd14a494d9f45
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I6ZUMpQpBj5oMtNfoz7145vxLgCgZEYIydmVJs8jje8mw6fcVE8PKGklo4zshcUigM4sTLfmz9irQYrufiC4Bw==