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
- dfa685e5b3a82ab1d45bc4b640e5c6eeaec7f62acff1694b55328f6599edba80
- request
- cbbe77574871fa94cc0e1ac7a958c3c36c3aea21ab72a9090703a370c0c3e6e7
- transaction
- 2a11f801140b0d5b48a6470120c2e9a46ced4850c0057a0fbb44f822778a0cdacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40059
the chainentry 40059
- sealed to the entry before
- 74a755a74fafa041640a20cb1d2724f626674bdc71293774bc99c1a8239672ce
- this leaf
- b40e6900e60bae57a0cc1a4ed9ea1273136d4ebcbf56a73af72f08ba1e1e1007
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Thvhe9DJ/VhlRmfPb2jKkgQvCbGMB/KvSEfsySrRu4Z55y7jmsH7cVnYs5gGhYrNIv/li8ib4PYl7vnGiEX1AQ==