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
- 8ee05bbf689fa1ac9cdb2f1eb7a44895b0f2d558b9c7b66082235f73dddde69d
- request
- 4b9b76b4ce03ce59a4f6cafe1754bf67c0d4903586ee7fac0f1c12e33b696dec
- transaction
- 956917c0e1e52a12a36fefc750912f2d60cd6f909ddbd4d2c0132c55eead3528computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29498
the chainentry 29498
- sealed to the entry before
- b5cd376427af77ffc6eb759da1c607d55aa6e28c4ef53f298465a90b726d8ef3
- this leaf
- 4896141a105901085039ca0f21b3ed523bb98bce3fc2b6a1036c1fb009e838ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3fOasTAvE3NP1Nk0QYmsRczl0YQiLCqsEjjPCJOmiBfu1LzmTDV/CGaFiYDf5gDmboPciy2vWFkqTOngnGnYDQ==