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
- c68017f478121209ce14fc68e74cbd24c1b772fe85d83a9f953c2194e9fed004
- request
- b6aa26c31e781bb90350ac2c85539c429b94882a7db5c7f418b233df03312cc8
- transaction
- d12a8907407259b34054f66216be084c2f26464ec0245a6a55b114bbb1a6f5d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71975
the chainentry 71975
- sealed to the entry before
- d491f26989ef3ae332c54d93cae62ffb810c0d517cf08faf5c00c656822ac807
- this leaf
- c11d3e227778be49f96357e5a3abd9faf04b9bc5429ebcba30f0be40a31a65e1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eHWzUw4Vj/gMkQguZdnoqrfEeahNiEl7BhHgtQ7cmH9DCWPi99qwlwPBzI+es7DbXIRf1JwJ9QTOyJe4uCyYDw==