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
- fd013aaf7ac45122df55caefef78818b1b799efcded26ac5acfe8c3d806786cd
- request
- 236ee8c7bbf7c5041ea67f40454fbe18c8005be7e1ddbffb41915c1e2cc10324
- transaction
- eff5112d1b3650e931565240a9edf192b5f36715014ff2e2641a50d64caa555ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31003
the chainentry 31003
- sealed to the entry before
- 5ecc0fe6f3591984bfb780d6a32dd43b3288f43e39c12a1fb3982189ace408f1
- this leaf
- 94a911c661ade0b035a097ffed463c6f664a90e0d54cf416f719e533035a056f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ix7TmmmKj3tnpE8M/Xj+VP2yoo2YDoV8m5RBVnXM0mfx2U1t3KVUww7BJzslC97clQpzLtZAvLYTuJ0Fs4QPBw==