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
- 9db2be8eaf10f172d18e262365e725168fb3667373aad838184966a88c479336
- request
- 8e0200651e33b2e214bde0e1253c3021e363f1fdd6254a2f0fb8ad5e9e9d49f4
- transaction
- d770d00d7e782d7008bce0b25418a34c849a2efc27d09cb05282c4b68b4f3e56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28083
the chainentry 28083
- sealed to the entry before
- 668aa902c0e04678c6225a2f2eec6c6c4c9833eb9f46e189d853bd7bbd3819b4
- this leaf
- 1a05dd0a37508973d228e2d239db301e6902ab451ee1d857122a66a5fa69a4d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- afK4Jg9x5iV0aR3CjvrCFh7IY1iYZhn4fAuMUO03ejQGn3kbqzyVcDLO5tQdvcsWSMusSS/Fuau4JNXcuQMPBQ==