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
- 358d9e66f502a682f98386516165e686b83853f0a2d97076b5ee2943da06fc82
- request
- 818c011ad732f24875579c8018a7e7ecdd6054650bb0c587e74e469a160ca487
- transaction
- 7c9f5c4480dd985c54fe8978e28a3f0bed26e09c16b67b490303725aee594497computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18964
the chainentry 18964
- sealed to the entry before
- b7ea32f99316d06fe1fe1dec0eb130f64fd134113115c69e342aa5ace14b2ba1
- this leaf
- f32986e7496f6f1ad313867c13f41cdad0c5ef99f121913322b33869bb027c0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K/JT1DR5t7sZ9YNkLC+t5MfV6Et07rl57nbKZ3eXf/yYEmkfrT51oOFq61V4zF7fcKoALcvBn9qN0arb9irUCw==