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
- df13c76bca7a1813fbea862c2c9a03a897bc090919f495d23f366929dfcf2730
- request
- 8f32fdb7f6cf113cc8c9b9e49b4043f36c326670142409be3eb12a5368b905c1
- transaction
- 19a67ee2574a621d1208efac11db2cd419a14d8f578fb626add6ea94e4511a63computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22790
the chainentry 22790
- sealed to the entry before
- a94d5c1e3d286ddba01d56be8e7f5e8886cdd609dffd3e14fbc315ac104b8c93
- this leaf
- 7d1ff056f987ca063c386b1ede56d2fbd1e55fd6bdb066401f74783840dafcc1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R9VmpekclCOtvDVQAvhJZmtk7UxV8khSLSH2PXXJ/6UcW96ZxJ1zSUX12ACushqzZNC2IeZmoH6B4XfTwb04Dg==