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
- 89fb02fb8ade8f0a0ca0da2ac98dd83995b9201f7fa54370359fe1729fb11414
- request
- 56c004555787b289d2efb998416c9e746942e099d9af2f926f06b50bed377c3b
- transaction
- abfc48eb1c08bd0a4d09c26397887fdbb8c1052b28d3dd9808424013cde2c26fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70756
the chainentry 70756
- sealed to the entry before
- 98ca37411ca21e456e98ee3677b1e62ca80b6b6902c314b92a23be1debaba681
- this leaf
- 75c7aba4158a44cb163c22caf9cd2aa9ff2fb5968cde711e65efd19512bf90af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gAUGN8Pes/igAREy4arjcdUZqQ6xNf+3YDXzlmV9CQnT1EtdFGBN5kO/2MoaMT/512gvk7qxOa9a8N37segCAA==