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
- 2f04099d769be9a513363ff38d2f328307e9c75d534657adecc18c42b67bf589
- request
- 6a8f390d1e9b468c5bc7c291bfd9d0cb95cfc9b7242001c0519328212f8345f8
- transaction
- 951cb8eb7a3c5a6b1dba00397b8a57139f6f092240805495dd001eaff06dd3bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47642
the chainentry 47642
- sealed to the entry before
- a225f5c19f05bf315b2f69ae90ef865bbd19f3919f0955439021b4b7e2b35634
- this leaf
- 8bef4e85dc5ab032be6c077532850f2f7227d6a74139cadc375f31b814d1a71f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uFHT+aK65+EH5xGH8NUes2LtM/FaRqRSfyTmwkWvQXwlyLFx2lBD4j8D5szzLS4gVTIJEZfBBdXDEE0+TkL6DQ==