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
- cf4d25b16411f3afcc5635d1140d7c02d6b37b47172fa7a5dca4d0c786216807
- request
- 1600bfc5cb4892dfab100347503a87a46947115188c3cafb65865e9b9c336713
- transaction
- 03e21ab4a2b1a04c17215b6834da4a18f305598ba30bd9d8c6e856722ffb019ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19565
the chainentry 19565
- sealed to the entry before
- 5cb0c1a774effbbc4bb3c4233b4e96ebcf4a631a72f6e68b1d35c1cd5160bc54
- this leaf
- cd273b55737d6075c44bbb7e4ccabf81c8b0856e9b992ca8ba9738946b0f54dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x7SiZjdTuyNm6OR6wsOMsy0b9kvFIEehWPKK3vPdaBfsVx13Z8FWvFSicoPmKv8CPan0ajdf/vzdLOw/DYCvCQ==