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
- 09373edd19f9f4da1846598fd9089c09c25d7a7fe61c0c1bfff3fe185d382176
- request
- f26b9a686e34cf5e24a4247687cb89da167cf071fdd05b0ca541494fe7a8d5ba
- transaction
- d92365a66a5f6c53d0ae491235e1e8938cfa5c09241575de2076b678b256a2c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63771
the chainentry 63771
- sealed to the entry before
- f50f22f615102e8751d1efa9d5b56a2663f5b876c7eeb86116903fe5d8784a5a
- this leaf
- e7f29fc3d1be6628656ad5eb860a84b0117a98709e2ca5dec0725324a3958fca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H36WynG0qgZm+X5P4sjbbogWp2Hlf5kYt5RKDBNABjHm19FBb0tku3q+kXn7WCkgn6N6a0/w+//E5e9jlvfqAA==