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
- dd9449ec8186593edb931877642e793e01696d97179483afc33740caca022c31
- request
- f4047becbef3355cc7019692784df1f44faf87c1fb94302a3ec5b5fe4eada5ed
- transaction
- a7f7d4eae3c186cc6c01d7991b500672b1117e17416c5a648f3ab596ac7281c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66470
the chainentry 66470
- sealed to the entry before
- bb7564f077e1972b528c3bae57842b468f3de4c9d0a681aa3a5eff32a0a6457a
- this leaf
- c300fe9d06c8b6d62db961cd37cbd162be03511a491b65a6a26f0f98fe43cc6e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EVo7Wc7WtMUpKHqrfsiBKEl0hp3MGFJarI82uqu00zJ/cRWIGQbjwUtbXw8lXrS16WnKkn0rrMQek09t6bKwAw==