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
- 0d9b52a97b21324fbc8ec2e6dd2d50d0abfb72ed6266cab6dccab335ad0b025a
- request
- d593940d9f34eb1b2290da27153faadffc10fe0576006607c9bc834ee8073865
- transaction
- 8cf5da5438eeb467bf22e2851854daf44df753610847c48b010b6897d9cd5f9bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13527
the chainentry 13527
- sealed to the entry before
- d9518f9d114c4b59902e56c2de5b79626cfc8bad7edb32b53f7f3ae8f0ccee99
- this leaf
- bd0a35458df667c01ffd04b87bf4e69f633e9ce59f32010e5cbbf0286e294133
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tZDGFdGNKsCK1tWhRj/PZZSJHbjioc0uuz6QN5NbvRzToGJLXpNTb7rRkkoKQT9qlrwz8v5gn0j+fAPoeLXxAg==