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
- ac0f1dc836a1cc318999406da810cf13d2be3171b82ecfdca52833f5bf92d6d7
- request
- 754390df38ad00aceb9f0f35b1cd33069742badb0eee735268832de19bdff1d4
- transaction
- 9b737045dbb3f7f3d843e1c3f3de9c2eb0068b6da4293f6154e4fe5ed17dbb99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61509
the chainentry 61509
- sealed to the entry before
- c78a1f6f4ac2bd1a0e24f313d303b120ecfd2bb3a0d6685080fdd8333d5c932b
- this leaf
- 0d57adaf1358e714a633445e7d521c6968b3e0404995eecfef58150fd9e2a8f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oSOAZ6ZuKKKD4zONPxYjsHotZTUfp9tL2oZKYCNxiv9pXhFYZASywTDf/B1pGvsygFU4gVkn05MHPn322rMbAQ==