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
- 10b5cff4deacd517ca41006126e6dcaf34ca6b7ccfeef550435689a7a5e8bbce
- request
- cbdc0ba559a43eee0865ea7d6f20094c427a8d24ec974bb1108610cebae5d022
- transaction
- dd74a69009db19d3260dff1a8211f8d0fd23011383082e608d1ad6217c14fb41computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55923
the chainentry 55923
- sealed to the entry before
- f2e78dc99824bba9d8e6063dddfcb0c0b3f80e9a234463c2a2801886b451745f
- this leaf
- 7af40c5cbd84f55e84351165256832c2595ba56cac7e62139271ac69dbde0d33
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KF7f+k2Y1GkwiRTAqz5gIEOcZf6jdV8otjonbdkyXVHbCBgHEgwXe+xyl5vdcAWQnKr94SCzXp6D8FnD8v8gAA==