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
- ad1cf139d90d3ccca5170272993a3b983a5414e44880644c099e2584901070f1
- request
- 13ad63d710490a6a07d3beb4901c57ccd0a5a9ae2284c1598cb049f477bfac8c
- transaction
- b778b18dc74bbf4294b28ba8e3016e0538b29a58e406a8c42dfb61b81ac38765computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28742
the chainentry 28742
- sealed to the entry before
- 59944a48656b2ba1fdd8bd0b8806c4c65336edb3e6410ed97ec29fbd6e59d9a6
- this leaf
- 69dc33514ec9c6db9f80c1efbd88e079e046223c319d1b400a0a3ffb92c5d20b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8h+Eowm72FnctmfptfmstlrHtQyHmffVrreFWM7rXQuP4jFSC8Nm/e20+JevlnHA2J9zL6YUCeUo3qHpxjmfAQ==