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
- fbbee79058b468d3d5c49dfdebfdd95ee48f3551e418d5e7135dbc6f405630d7
- request
- fd7cf40c845a9c13a38b70aa794db341d925ce4f1c16c48a5859814f1bf05f51
- transaction
- 9bf24e9e0080d830363e590e9de9eae0e9def3f8449470d9d1daa5b05295efdbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34259
the chainentry 34259
- sealed to the entry before
- b407c8400cf7d8cde87e59cc6f567db73ca44b8e5afa86c23ea9fff9b8399223
- this leaf
- 89948fc6262c5d6aa463edd9d1b5e315b8caefec8cd755318832b1808547e827
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- spi9vq4nIc0TYLL3iKO5/06cF7SFJfwi1UxDUp2rJ6f8Jc1d3Uj9IZPoP9h0NJ72EPKBikpGzwAHfU+vn5PBCQ==