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
- 7e1cb9624d2be728d34ce75ede76a9ad120de01c781db975612e540b3d2998ef
- request
- 9766c786dced59b338815f0db5331b0beb7566e48b00dad1199e8d15d73d6595
- transaction
- 4bec55854b113e61424da4180cfb998641166cded2b564c88f743fc6c92d2843computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61008
the chainentry 61008
- sealed to the entry before
- b24a627ceb7a7f60ef049ca28ab2a6cc0b7dc4f2ba5fd385962fc47dd4d18d94
- this leaf
- 7a94e6615c00e71543355daa3d06f680f11a3b6a09f3ba311ec53c2246f4126c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z/GGIJ3lUL/yXlL92oB8Y3+eprvJp4lsf2xwbHK6uQUPorvm2nCYqe9f8uISJQqvwPA0Se738V2e6wmu9/d4Cg==