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
- a8198922dfdbe1b06a67b3978638b8002fd48fac9103ff2b2c38b31f54811e3f
- request
- f03555bce4e05be018d1457add89760b7e134ac8ea6ed1028efb6aba09922884
- transaction
- 26bf1aed24e3f8c0a3a45de986880e230c07a95d9644fd050330866f523348f0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60304
the chainentry 60304
- sealed to the entry before
- 2a8398320268841d7dab9196c7fa93e62e525fbe6e9424e4b5070588dfaf0a7e
- this leaf
- 26d11b0973ea7edbcb52127ab2ab1f95fda396603105ad94b6cfa39cc02317e0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LKjdHbqNuM+b2hjlkafgYfEDL276Ib7PlX9BUIkW/j5qQLqblmzDRKujgTwbDFR2ZMb96pn7tEuQ3SD/jARBAg==