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
- c00ff6edc699799dbde7d56f193e7fc4fca8180ddad2f3cfb1b693bd676a10ff
- request
- 46dee033fad86249fc6291a24d47c9821144f4a85fc03a2cf0dcb07ea5fd0c3b
- transaction
- 2ee8f3f6b344f4e72c6885663f652f23562573745492f540cb4f74b7e24b643acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42829
the chainentry 42829
- sealed to the entry before
- 7e6dc03ad7b46212db9e53dbba2573561d6fe682de7b9ea37a6d70b9272c13e6
- this leaf
- 3eda8b76bbf961b113399237dd5c061ce047a7549f6dbcb891541a89d87f0ce8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lq7D2IOIfmerrjdDblvO2ExrLglCvkwtDC1Zp7og87VqnekUbSv2VN9A6vH80jWIdXZXdOXeQIy5i1sYOk9KCw==