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
- 9611c43a9e48fcd1c87d5f54097aecc98e8eebb190745c4ed43fa0a1dfc027e9
- request
- 9f73529005b36f5b31dfc2a3e20764cb1559cb1cecd80ac84c49514f3a9cfebc
- transaction
- 27ff93f8229390077496fe712d8a50c74a7a35079c4a6506f1f0bce5edf1d06bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38453
the chainentry 38453
- sealed to the entry before
- 5c337cbe6ad77ec475142e4b9eaf3b17b2393e77a70c8bae6082f5bf2e5afb3a
- this leaf
- 8c3a363a56d003846a337a64cf4b8bbe75038fa9a95188b1de69a0a92587ea2c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6PsfDUtqcNyzMnLHkWquuCitSa0+bSIzPtCDenM9lLwOFbFTWOHRJVjdpO6aaE7foGwo4qBlwxxWlKpjNPyRDQ==