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
- 4e61bd33eb1c52dac1ecbad0403f73f3b0b89af2eed36db3406c586cd1bab308
- request
- bbca2b5c46794f73d0914d12241e84e0eb76b384ce9a85168f79f24891ba0615
- transaction
- 046f06434da4112badf02d9311e4164a862f77628a0bdf80faa6cb9470ab811ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47835
the chainentry 47835
- sealed to the entry before
- 2ca456c5ced4c3045e7ed43704b65f8498ab6f47b9a01e7f255e169625aff0ef
- this leaf
- 557ee8864f13399ac2f9f4dff04cd6696b7ae1e4d365a92276d2b7a072f7b0b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dkrEbAQa0Yy1jOMjudMu3CYxb2lxiQgg5fsK/yQfT3mfkBYBLZlFjjV8J21voAIeGT4p3BS13nAEPaLfUeSmDw==