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
- ff9ac1b0cb7c6723ddf199eca4f5724163b3fb97fded2a07a70db962ded7df0d
- request
- 844f6ef2956fb96e6cda01c45f048f38606b9ac93fcc6cb957ede878d833ea8a
- transaction
- 2376aa56763ca28e34c6b425da3bc4e60b2cf7f86326aae4a987dc0cc03c6c02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18050
the chainentry 18050
- sealed to the entry before
- c9fac83dc180648d5e092ff4bcc583a88cc03104f1175dbd35d1d7eca87d11b0
- this leaf
- 24d30a8269578a196f15b012df291f09c9a438e79cfd9f4031eb200da0208938
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZEypqssxfno9eRk/bNHygfkAhvCffpFHy9s4hOGacxxdrLaJy4VsrjU88EIvphOP81cz2Kp91qJe2ixqxRk5Bg==