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
- a2000d263f8db106a024702c58c8cec8e38396be9c63cb7b36dd8ce91787219e
- request
- 0c281e3523241dfddef88d896976793c06fc591ed8e9733df0042fdf281e9852
- transaction
- e1377ea49370315b7bdbe42d9b3d33f0fdac929d8a798cb9cb6418dd03193ca1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70620
the chainentry 70620
- sealed to the entry before
- c277ffbafbd2b35cf66f46ca7b91891c10e53599fc7d5bf40d6fe00134a51f23
- this leaf
- 0d3a2007f9cee4db50aa7ad187267641c23c6cd32fc828b8ab7e8575d260f09f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qSYwlNKHaz4UfsgaFOeCYaS8dXvZg8H1qFYrHaZnwSYG3RKlUqvePFCYDnafnGAbj6KCK7gf6SSC7iAq6iRJBQ==