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
- 043d994fe5afdc9d56c6eff9bc0fe1a4d9f049f25eea901a411a2c9882846ed3
- request
- ede97cc57930201bc55d68aa7c6f9544238daca93c67cd2208dcb354ca96faa9
- transaction
- 5ba9150b4ac6b7265d49b22c007e76cde780dc55dd8bfcb4085d06adfa5fae23computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59107
the chainentry 59107
- sealed to the entry before
- abf559238849d3b6ab676083839cfda397cbe24ae12d45e0055683798d7353a0
- this leaf
- fd06ac91c2dde789c446560535341b3ce8d8795c0cd0fffc4b524ff8745508f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cVTd9seNCFojfiKSG5K6zhjOoahDQQZaS9lb8iNzb5FkOLC2OYsYnnG1eIcsvXaUE2Ij9adCrvnXSl2JwU8ECA==