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
- 73aeee8454ce00f328b5b75f47d6ed92487cf665731d135d907434a166b4bec6
- request
- a0d56489166b11040374f9bbaef4ae0bc24d21c7a006b7cadb629798adbe27ec
- transaction
- 611acad0313d43d9ba348e50181b5c309e09f4156dd52b7be86f15f3eb653f49computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27935
the chainentry 27935
- sealed to the entry before
- f23e942a65f53ed6d7b86be6522b04336db72b0d8808437e232e07c034368463
- this leaf
- e5a2fefa573471bf7554801fbe46bff3578b3b18ecd257b88b49e40051625f2f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3CZcvmUlq4Y87Jox6lW59kGdLZUC/gwqhhW+PCo2rUGvFd/S9dEP55kIyGxkYxspljVcIYcSigCyu8lCHc+fAA==