> 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/help/faq.md).

# FAQ

Short answers to common questions about checks and results.

## What does "near real-time" mean on a check?

The check queries its data source live and returns a result immediately in the portal or API, usually within seconds. Other checks depend on a third party and take from hours to weeks. See [Data sources and turnaround](https://developer.fraudcheck.co.za/product/how-it-works/data-sources).

## What is the difference between on-file and online identity verification?

On-file checks read records held by credit bureaus and other verified sources, at lower cost. Online checks query the Department of Home Affairs directly, for maximum coverage and the most current record. See [Data sources and turnaround](https://developer.fraudcheck.co.za/product/how-it-works/data-sources) and [Identity Verification - Enhanced](https://developer.fraudcheck.co.za/product/verification/identity/enhanced).

## What do Accept, Review and Reject mean?

Accept means no material issue was found, Review means a result needs a human look, and Reject means a confirmed match or failure that should stop the process. See [Results and outcomes](https://developer.fraudcheck.co.za/product/how-it-works/results-and-outcomes).

## What does Match or No match mean?

A field-level comparison, for example a submitted surname against a Home Affairs record, usually rolled up into an overall decision. See [Results and outcomes](https://developer.fraudcheck.co.za/product/how-it-works/results-and-outcomes).

## Why do some checks take hours or days?

Turnaround depends on the data source, such as SAPS for criminal records or Umalusi and institutions for qualifications. Faster variants exist for some checks. See [Data sources and turnaround](https://developer.fraudcheck.co.za/product/how-it-works/data-sources).

## What happens if a check finds no record?

The result says so explicitly rather than coming back empty. See [Results and outcomes](https://developer.fraudcheck.co.za/product/how-it-works/results-and-outcomes).

## Where does watchlist and sanctions data come from?

From South African and international PEP, sanctions and crime sources, such as FIC Targeted Financial Sanctions, UN Security Council sanctions, OFAC, EU and Swiss SECO sanctions, and INTERPOL Red Notices. See [Individual watchlist: basic](https://developer.fraudcheck.co.za/product/screening/watchlist/individual-basic) for the coverage.

## Do I need consent to run a check?

For almost every check, yes, and you keep the proof. See [Consent and permissible use](https://developer.fraudcheck.co.za/product/how-it-works/consent).


---

# 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/help/faq.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.