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
- bf1264a35d70e69b0637854a5f623c448b6dd1419610be77ca56421c6cf41bbb
- request
- d2b8487dca9315bdfd932d5ccc6ce8d0855ffc36fbc43bd0d32f61662ace9d54
- transaction
- ffd3044e3e2252322758cc38b289b25fdddf61087f17c9a22874ce6fad617776computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71636
the chainentry 71636
- sealed to the entry before
- 3289807f8d2b5cc951d583ff2ce3683f7ff6222c5463b3724e41cc0db264c779
- this leaf
- f62daf5329f784d74a6e29e12ab319a03c4af750a5215d3f107b60a9da0bf493
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pGpYNGpJb0X0rOQSPRYjmNSfZ+nvLJa0LgnW3ITnDLfEQ5ovz4qFhGHBKoQn3nFlIaCqwjnL3AtA1HnKiH5CCw==