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
- e4bf1b22a24d718d8f8a918b2c48d8cbd924d5e71bdb04c5cd86063f47d06bf7
- request
- 86ffd89b5aca4549d4aa6ed15af489af5176ffba2d81d8e81ecd3f506343c971
- transaction
- 449458a82eb8c403b7e5ee82ead62d8fdf7c74aad3f087e449d3b09d2d5886b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65403
the chainentry 65403
- sealed to the entry before
- 0766494b6477f231baddccb81396dcda3db010b9b185471a3d3d4f4ba6c85a92
- this leaf
- f6d76a53eaa86832a72e413761c89f6dc549595963b239a511de20c8a4cb59ff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /eYO469z/TXMZ+3Ep9Gbs/XikNgyQzRXVlvyp3ih/ERnWOexsyoC99Q3L8xt8cmxyez9ZzXEnXzX1PreqJ20BA==