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
- 6db6a97ccbb74a374af07d558f8d3e5647b6ae7897f1a602758b2faacdfb362c
- request
- 6d81012dd17ad1fbd681901f8175a2994510581e63bf7ef133434956af4ce3b0
- transaction
- bc09cbc292f3249740bd08e5a7dba905304bfb78a9d9bda5647c5fcb567fae6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22612
the chainentry 22612
- sealed to the entry before
- 48b86e27b01b6cc187b97c683acaf9fc6d938fe21d7b1ec6d807bb207c1342ef
- this leaf
- 3a2819ce39ed3f21139dab0a71cd2df86387c09e5fedff010d43050938852010
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NVRWttauXVVhwkRH9LiqMPk9RJsTs6evex2/XVCy7NNXhieuzaIYfUxe9Vic1LsxszNmgoGLkY0o7uAZvo2AAg==