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
- 48ef53a39cf0acaa8077fb8bb154460a07a83d2771fcceca1bbd6ca448491207
- request
- fc73a2e36aeb052e5e5dbb35afca71f6383cd433403e077894df41459cd2368a
- transaction
- 9069a3b49b001dd2a81cea76fb3f18697386031a0e3ca711df18f77bdac32b72computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5207
the chainentry 5207
- sealed to the entry before
- 8050407bc485ba4abefae09e5494ec4fa27300c2e3c6b28443a8da7554b045b9
- this leaf
- a56ca03840aaf24b94255bbb63ec33576f3423e38f853a3f8b3caeb00c486732
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E9ZpCtcfnAOM7eGG/BvtzKTWWH+39UIfVtg8qYP8WNsloR4zEfS44nyuUcoFJMF9tiqFqA7UMhUs9JElwAbzDQ==