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
- c588a7de0d90e78840a1b00986aac12ab74c194c6e47bf3c1d51c4e41f0a2b74
- request
- 1f7ffdc79a9fb683e1e188b35940560b657b39dd63f4fbed4ad06e0c871d6381
- transaction
- 22a672393726539e5ee7c09fd4aa77284cd01999e15d49534e77bbcd75e4bb67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66246
the chainentry 66246
- sealed to the entry before
- 088a7b29b68a45702c3517a02a3b1f2a791d295ead5c8fdb54bb67b661e12772
- this leaf
- 3eea929f8bc7ab6191e4fd04af46dcb64615d9c86114015e436a4c15488a6f97
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xEcM27cCixr4dL5Hk1WiIMk+25IgGZN2DAGhqy7CYIZkeFZPQKlFBIVQV14b7aTwNnoBasQpewTjmYKL5i1cCw==