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
- 1bef7e31acc2f49392b362bcfab8addfd9b50250ff5680ef171e17004a35d551
- request
- 7fbf256064d0f1fe4530bd4f9700b3817cd1b55926f268da914e9a7798bb6f7b
- transaction
- f50c09eab482188a76591db1a5bd725f7d2c1d92178dd7ed330b3594c0e801c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43684
the chainentry 43684
- sealed to the entry before
- c2511669a5612630f29c4c9a41b6759bbfce936f2cc9ce5e35177687378964da
- this leaf
- cdabf0f7bacca33601928f66794a65991f45a4e3a9aa683e5044ca1420b8925f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ak5eOC6R8Qp3xTMC+OhI4mUbBN9fqxy2nHVremY8hRnwSXf6moe9uQEE8XuguHA4Ql5tmoyYkMs4EXjcaAFDBw==