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
- 6a7143cf8db47742b93ffb01d3711fc0c959e2ee9146b5ffa47953ad8d087298
- request
- eccf08bf9422928081ac6ae5aacb02089ebb59d4ab3d53140b856023875569f7
- transaction
- 9e2c772d6ddbe48159259ddad06d001131e05411b36e56f931206c8f6c7bcd99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21938
the chainentry 21938
- sealed to the entry before
- 15a5493f60cb74428ea2df7f0e63bc66fa7ff158e7845348eb9df0caa3171b19
- this leaf
- f18b87071b84678ddd3a2ab88fda9cad25fd0bbc6e39f729bae11a625edf9bcf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sAbj712azaXfAqNB1ZQsmM3I1iaaVDFTtrk7ZEhjped1q3/UWd22FBIY2FuY8QyEAnid8sviSWiWucm092JBDw==