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
- daffbb3a008cf751b8ce7a237a43484c50a713acd944927fbbb7a4db1e133ab4
- request
- 62fb38c2f86af3e2c1902c9438e65411ef9b142485397247bbda0f4d616b42bb
- transaction
- 13fede421a3c49f0af93b5d709e678ed213a3a78bdd6260c6c0e4d0623d45069computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30023
the chainentry 30023
- sealed to the entry before
- 5beff68b480c488bfe44e3ba9a5df70457280194a25aa53f143c603d6bd9605f
- this leaf
- c77642cb1a9dafea5d18577d57eacc09810cf9d2ad80c51a08c402150163e80e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y2hoQ57Si1RkqQnaWNpB4wjqLoNRsEZDrhIibFmIT2XCk54YgJtKPeQ1TC6KWm3C3L5pLpOkxEi6uJmJ7DnbAQ==