> For the complete documentation index, see [llms.txt](https://docs.fraudcheck.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fraudcheck.co.za/product/products/screening/watchlist.md).

# Watchlist, PEP and adverse media

Watchlist screening checks a person or business against sanctions, PEP, crime and adverse media sources.

## What it is

Watchlist screening checks a person or business against sanctions, PEP, crime and adverse media sources.

## Products compared

| Product                                                                                                  | What it returns                                                                                                | Subject    | Channels       | Turnaround        |
| -------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ---------- | -------------- | ----------------- |
| [Individual watchlist: basic](/product/products/screening/watchlist/individual-basic.md)                 | Screens a person against the PEP, sanctions and crime lists you choose, with optional relatives screening.     | Individual | Portal and API | Near real-time    |
| [Individual watchlist: comprehensive](/product/products/screening/watchlist/individual-comprehensive.md) | Screens a person against sanctions, PEP and adverse media sources and adds a risk rating.                      | Individual | Portal and API | 30–60 seconds     |
| [Business watchlist: basic](/product/products/screening/watchlist/business-basic.md)                     | Screens a company against sanctions, crime and financial-crime lists in three coverage levels.                 | Business   | Portal and API | Under 3–5 seconds |
| [Business watchlist: comprehensive](/product/products/screening/watchlist/business-comprehensive.md)     | Screens a company against sanctions, PEP, adverse media and regulatory lists with a scored, auditable outcome. | Business   | Portal and API | Under 10 seconds  |

## When to use which

* **People**: use [Individual watchlist: basic](/product/products/screening/watchlist/individual-basic.md) for configurable PEP, sanctions and crime lists, precision filters and relatives screening. Use [Individual watchlist: comprehensive](/product/products/screening/watchlist/individual-comprehensive.md) when you also need adverse media and a risk rating.
* **Businesses**: use [Business watchlist: basic](/product/products/screening/watchlist/business-basic.md) for fast sanctions and crime screening (Lite, Crime or Extensive). Use [Business watchlist: comprehensive](/product/products/screening/watchlist/business-comprehensive.md) when you need adverse media and a scored, auditable outcome.

## Related guides

None yet.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fraudcheck.co.za/product/products/screening/watchlist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.