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
- e42cdcd4ab8da1ef298c949b36457dccebea410b6b12c6101c99d5f04195fa38
- request
- 58df1b96a07f9807c39d537b5994281916e179ccc2256f408a46f5c50584c927
- transaction
- e2385316f2bd5a14d4f4ab1900b3c3bb2af7467e065cac2bc387ba002ecc6b6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25541
the chainentry 25541
- sealed to the entry before
- f85465dadee549e7985ce48a644c16e81740dc5a7c60cde63b32d4604923b007
- this leaf
- 683f95a35f6e3b6453a54296205e3c7ccb178a1bcc1a22ead39af6753d51fa92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /nK2VSpIGZz2h+GBR+wLjhAJLLmrjBobL2wz7n+fws9X2OlSCxtGPXc7z5/ZCPL3yLhoc7dBCG88IbceAIWIDA==