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
- bd82aaa9cbb9371f6f95826fe3893025969f4d8fa1852a2916be0f1bdca4ce94
- request
- ef4597c2083a565ba826d55e252ffe295caf8d38d680df14b2b3f891a6c37c33
- transaction
- 2db58a99facbd70f96ecb995adf1c8d023efe6d69e6a64c5e27b180e2fd78ae8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32965
the chainentry 32965
- sealed to the entry before
- 25ff8a36de8f512e81de5d8fd2d92113f0c493202964600a9f044a0567176cbe
- this leaf
- 4e973dcc9c18aeb6ed11e5fa7315963298642c2003bdb3680eb7cbc5f9da5446
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- buNOLSUGzAYWlnPtjeBo/0uB9F6DpLu0NS8oOqnJqiadLZfemxGRh9zYsOjFn6zdj76vOsROBhEO4OleDvpPBw==