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
- 04fb417222f4042c2c407343e1d20e02bc37b7266e2cf758dfd1df32072f139b
- request
- cccdbe29379441f637ab30d5e81a322ca521347cdcc157b3a8c36ff98e6c48b5
- transaction
- e7ac3b4ab50828986d4745eab5cf7e5a5fa9fbc810cb3a111e6506a405e3f753computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45223
the chainentry 45223
- sealed to the entry before
- 11e63f4c22fa837ba4b766e9ad851791328ea3710009a3f31e453f111f8c3cbe
- this leaf
- 16af7ec6b549d80260ea626d881c16fe7b3472e11b7f6960870687d3466dcd01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RWHmGZ65mR7IIiakGafbYtAUNsmU/3XXSooF1FOdOMZXzpHyVSqtYzgrjZ66auf385RdHMM2XC996SOOZu2DBQ==