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
- 9093c27bd0a56ac41c9e2822fbc8df7078d84217f412112c69d209f05ecb5001
- request
- e21fea750160a913d0e73bf547b021ac8af6eb06a59cdad1c28bc68bb0f73c08
- transaction
- 0b01f57ccabc92e7ba738d43f1e4e58235bdac44f7225afb6243f7e1ecc0da54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73255
the chainentry 73255
- sealed to the entry before
- e3ec9978feffe767bd668d008533b47a0fa6a22bd8e2c2d8ebda6191c14c5663
- this leaf
- 71a97e9d6a132468d181927d11669844b5365eba40e53de41f57957b74428240
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2XwyZvLbd1eBAmflZsXgQIGZU4jN/PfGhTkbTWm3KY0t5saPc9JH/nuHaWz1NoPwgOHQbnwmF0CQUQKihkxMDw==