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
- 2473639a4e395877e0cc0c5da59bebccd6d2a8084a0d291a10dd9add7c860d7e
- request
- e41268449fe838b1de63d0663863498e4b2dd6bfe1bb2956e8805fc5f32ded16
- transaction
- fadb73f3940c815dde80b3268617d6e6f3b0e0ed3687b68ee5304bfad9e25fd3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51827
the chainentry 51827
- sealed to the entry before
- 5f0ebb7cecb1c86b9cf2ff81579a5e20a6f96e9ca2d1a2e278387fa80b30b055
- this leaf
- 99b572605920693617e2bb54bda758aa3bb1aeb73c79f7a16931565fb1c3ded5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pyj8HMs8bGrwreJnzpracT4EbsC7KzuvpkvZZtOV3O2vkM53bbpjtrJSZCKjkvJrNcCJowPBr2+kT4qCMBKdDA==