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
- 3e875eb9a1ec7e1d6d09bd301e528c1c175306b2adf8ca0159ec0b76c2baf1a1
- request
- aa3494ac2e4440bcf6dd2376c8d74c8fe4f12584d20dea587e3369b4803ccb64
- transaction
- fbe4698f00715e639f2ac66362198ba3fdf2774780a0c10c9ff9b2eb8e31b307computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53830
the chainentry 53830
- sealed to the entry before
- c9eb0cb8a4bd65e395f64eda8021ea9e05bedbe8f017ac640c31eedfdeab6312
- this leaf
- f6bd1ece62aaa0037a90b387950a11dcede2687f370653ea5ced1859e567a531
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /M5ObtwyX370QJh5BJH5BTfnMXbfhGwfhFkg43C6NYZjLFKhnwn2LufYdAT/OwwLKQOEHiLGWTaEbQ9g4nSzAA==