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
- f198760acb647f6a7eba0c53736c3056d03b8dd9194df397466fb0df0ed7ea53
- request
- b33f48529ecf026fe1919415468245abb7779e8dabd0f36482541a2038004fc0
- transaction
- aa265c7edc434257680f4fde2e52f09dff5c71e71b48055826a7dd7dd33bb198computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39251
the chainentry 39251
- sealed to the entry before
- a4d5e253d03b7d1737494f3b5e8334c50a58b9cb4d78c8730a1f076955b8baf3
- this leaf
- c4bfd24c5e865f0b5b13bc56814bb166169dd5d663e04f8e1b23942d82543130
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CU5Mns3waxdRcxU52Lbduhocw1ejwU35bZo18nzEIaY6qH6y1Al1IwubTfHzfo7MiIEETfyUuVt/EKfYIDMzBQ==