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
- 60dc21227584d4796bc2bda3f9d3202e571e962b69db9a5bc7d35a5d8d15097e
- request
- 7ba42d671e23e4602411e8bcaeccc09e70b772e93dc4094e99d3e88462791c2d
- transaction
- 4830033b96273c098019dfbf8fd8e2a3edf01877e3cbd542d0ff925556c49f28computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58873
the chainentry 58873
- sealed to the entry before
- 6a7bdc3a50460ba028fa3db53feb1177f2d44edb59048e10785ba34b54a90090
- this leaf
- 206696a09974c6f74b6d9b6774c0b5df4bba169e964b1d2e6fb7861263eea6d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0ffQOsSibIfZNi8smPDls1SE/it1c1vPxSPQ4ss4NP214aiUfrXiXAfPR8iVU1MtiQ/GoaHaX5YiZQ7eQARTCQ==