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
- a21e42d17a3bd36de268c070f772dac2e71db6a83db5fd7c54e5ed3feb6b420e
- request
- 2e7f392ff3115139cea2eadc489e339187c1b0eda8ee7de48f4fbf38eb231a99
- transaction
- a2991fddc2f34d906275007b091eb0d63627534a4d72a97d016b5e3750ed0003computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26664
the chainentry 26664
- sealed to the entry before
- 9406c87b302946907ba1cfc5475397a4795613afddd53af58c1dbbef40040a40
- this leaf
- e26749c46e535a272265dfeaddf38de30db5905a093cd50ccaa3452364794d44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GpWFztlRSbsDNc+v1NvXQKqEq5eBIJNhnHNNGqSPUHsf2weQ2oYmA9jydQCHBz2u6AykNQHsmjE7f3xW64/nAA==