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
- 8091cf5ca63924c3746229c24a5c38725a4ac7ee6d6ffc5039ebae61cf1aba27
- request
- eba36ccdb2609b3d8a2ea6f6001163270dfa63c6c5f667800f762ad82650fe27
- transaction
- 1be3eecae9ed0d7250efe7ae1f64d5b112d090c0209a621cd5866e5a1efbc7e8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60067
the chainentry 60067
- sealed to the entry before
- 51ade78331a2e536ae11db6dcd4a98fe7a6772532be307d2b5fbfb930529557e
- this leaf
- 1dc2faec8fc832d1edaa490676556c701de43ae77eabb6526d0b27d96b1a9b64
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +wqiPv8jSvXW5nZzJNSQ5XjHBlrZQn45WmSkFwD2scI0UbJXEPUfh6WFNnG29YH5CQQyYrvG9wJHYN/b7qggDg==