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
- aafd17dd670c3626ff505df694e336bf9513e0c326a2494cae2200f903c29ca0
- request
- aadcfbc65858de0dbc304cec725f1009720b5acac9e9816f194a9b9fff02a5d2
- transaction
- e40ef15d9aa3b24245869111aefe10da1862ea06d1c59c612a64d0c5f4ff960fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57599
the chainentry 57599
- sealed to the entry before
- 7fedbf2c44818ec86b67ff71466c8e88739259744a8f7001af10d3a87ed5637a
- this leaf
- a8aca2966fb92a54c09fbdcea1a8512e2602ed89c4704005ef832de3f3eb6d9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wDdD5rHRzB9uwWUZrPt+z0iWOlazwXlSHqXjDYt51MxY3qsh7Srb8f03Is5A9DQn/uWptC8EZf8HJkj0U2rJDQ==