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
- dd61c76fd3256f657aa37bec9e5293d854a8f5e1f15c9d15bf59f1aafd38863b
- request
- 3d9f35759c0ff99c83a80382ccf20a0ddb57717f3c06a0274bb937acf7093d74
- transaction
- 1a05c54d6ecc5ecfebaba0ce03565481b0a3a5629306c41ce248ee10ea11e8fbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74680
the chainentry 74680
- sealed to the entry before
- a7297e5b8ea9a3d3575063b2cc01bc5e4628e4b59b56e9ba14aaf9f38995cb16
- this leaf
- da224d51ce3ded2947827dea6d6d69e29a9e7ed32eac57cb28c0004d2a89e611
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D1rrwq0b2Q9QnCKA2+Np0Ro1ts6VdXirNxQKZ/RQHzLueV5k387an/0GiJIBbFkyJi1MiNN2JEaf+ChUSHTeAA==