> 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.md). # Screening Screen a person or business against criminal, watchlist, credit risk, fraud-listing and self-exclusion sources. Screen a person or business against criminal, watchlist, credit risk, fraud-listing and self-exclusion sources. ## What it covers Screening looks outward at a person's or business's history and reputation, to surface risk that verification alone will not catch. It covers criminal record screening, watchlist, PEP and adverse media screening, credit and financial risk, fraud listings and operator-specific self-exclusion screening. ## Capabilities * [Criminal record screening](/product/products/screening/criminal-records.md): Screen against SAPS criminal records, the Child Protection Register and the Register for Sex Offenders. * [Watchlist, PEP and adverse media](/product/products/screening/watchlist.md): Screen against sanctions, PEP, crime and adverse media sources. * [Credit and financial risk](/product/products/screening/credit.md): Assess credit risk with a score, full report or business vetting summary. * [SAFPS fraud listing](/product/products/screening/fraud-listing.md): Check for fraud listings on the SAFPS database. * [Self-exclusion screening](/product/products/screening/self-exclusion.md): Screen players against an operator's gambling self-exclusion list. ## How it connects Screening usually runs alongside or just after [Verification](/product/products/verification.md): once you know who you are dealing with, screening tells you whether taking them on is a risk worth taking. To keep screening results current after onboarding, use [Monitoring](/product/products/monitoring.md). --- # 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.md?ask=&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.