> 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/overview/how-it-works.md). # How it works How Fraudcheck checks work: channels, consent, results and turnaround. ## Verification and screening The two answer different questions. **Verification** confirms that an identity, document, address or business is real, and that it belongs to the person or business presenting it: it looks inward, at the claim itself. **Screening** looks outward, checking that same person or business against external sources (criminal records, sanctions and watchlists, adverse media, credit bureaus) to surface risk that verification alone will not catch. Confirming someone is real is not the same as confirming they are safe to deal with. Most onboarding journeys run both, in that order: verify first to confirm who you are dealing with, then screen to confirm there is no reason not to. [Monitoring](/product/products/monitoring.md) then keeps screening results current over time. ## In this section * [Ways to use Fraudcheck](/product/overview/how-it-works/channels.md): the portal, the API and digital onboarding. * [Consent and permissible use](/product/overview/how-it-works/consent.md): what you must have before running a check. * [Results and outcomes](/product/overview/how-it-works/results-and-outcomes.md): Accept, Review and Reject, and immediate versus pending results. * [Data sources and turnaround](/product/overview/how-it-works/data-sources.md): where results come from and how long they take. --- # 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/overview/how-it-works.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.