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
- 603f0ffb760254a4f3efcc77d6db6fcff06eb18818e52b151737cdc34e765da3
- request
- f777d23b3e41952fe1a1476a49147d959485662da8fedaae918e20cc8cdb09f2
- transaction
- eb3c3aa5e78f979a3db4b881bddaf9ee273ff5bfcde1fd0011f19941f74aae6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56707
the chainentry 56707
- sealed to the entry before
- 419196082131484f6f8a61aef472e51b0cbc9f3fa9356e2ca7415d5091031aaf
- this leaf
- 01a6c4193e02506ec6f7f4ec18c800e59d6175523eed57b181e4687756296120
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aClgInG8O4aM2VCuMpXhSVTJSZaW/R20JhOdwD025xSILjGmsSPWTsQJ276dA25yL8cfy0C/wpw9BjyTZ9O1BA==