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
- 445f1b09194ff08d2c7e2f381b880eaeac72001962bdc420d64a8230015460b4
- request
- 02d855e0e3cbee2ffed32a5893af730dfbbc9babec42aaa3f7bb1320dd1af47f
- transaction
- 04c95fbe84885b2b89431944ef80d857ef65a0fc447329eb2d56ccf72aba928bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72042
the chainentry 72042
- sealed to the entry before
- 27ad4a17c8687709887e52c95ce44db3406a97aecd8953571a2089ca516ddc30
- this leaf
- 2f03721a4789e1d0c87638c62bab8808aaf4e082cd14581320a5969304198231
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2tqzAErXOSYMhOHu/ji8jjhjCxXZbmI+w+QU+GavkYfE6amN1+IBfYmVHbYUV8wMP/xtj7cjIffhtp1ARZVBCA==