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
- 295dbde20f74bdf49ce048ffdcc9b82a1ff2bd34837cbd264c9c563080c188df
- request
- 2cbbb0b9ba9d46394cc3a46ae10b91672d560df811860751cb1fcb26c8e308e0
- transaction
- aa5cc7465a1a3690579a584a7b2c2a70c23974fbcfb1ebdf82c23915438cda38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61759
the chainentry 61759
- sealed to the entry before
- 411b216d2045ab10b1ff3d30b8e43cdcb15fdc036a814b853364887b7313bec5
- this leaf
- 286ece5b2016c6eecaf261104ba6055ab9316ec5635eb3f9d6dc21c85a6a8e81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zF0Qla2KDxa4+ZcIaK4G8LkNpRHxGgo/vNDAclkIJvF75ui6dHgWgiiLgep60wqTcqTV7epInyYYewKFAw+dCA==