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
- e7cf9d544f181935de0b81fea6ee7ffd7d254c1864193ac0465027116a61b003
- request
- 96002c96870edc92be53de82d6f5506cc15237397cf501aade596045376be631
- transaction
- f84b5dcc92fff60ff36491f73826e9470e35133444c7c84727545dced729d91ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70992
the chainentry 70992
- sealed to the entry before
- 960bf67f9c4828e2fc35dd55aef392b5d6247212e6fd8dd39e812a5be9308a73
- this leaf
- 8e9cfc81bd242c7eb5be06c13c957ad5bf3da84c30959011db078e880d2262b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GfI6vl+C32sYOpBZ5hcd2QHipaXAMFaTJ0gPW6MZwwRLz6gSwebOMWLlnKj6s9g71VYLjno0LilDm8hEcnSEDg==