> 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/results-and-outcomes.md). # Results and outcomes What Accept, Review and Reject mean, and how immediate and pending results work. ## Decision outcomes Most checks return a decision as well as data. The most common decision set is: | Outcome | Meaning | | ---------- | ------------------------------------------------------------------------------------------------------------- | | **Accept** | No material issue was found. | | **Review** | A possible match or borderline result that needs a human look. | | **Reject** | A confirmed match or failure that should stop the process. | | **Fail** | The check could not be completed, for example because a data source was unavailable. Returned by some checks. | A Reject or Review is a valid result, not a failed request. Some checks use their own outcome values, such as *No record found* for criminal records or *Suitable* and *Unsuitable* for the Child Protection Register; each product page lists its outcomes. ## Match and no match *Match* and *No match* are field-level comparisons, for example a submitted surname compared with a Home Affairs or bureau record. Field-level results are usually rolled up into an overall decision, such as *Verification passed: Yes or No* or Accept, Review or Reject. ## When no record is found A check that finds no record says so explicitly rather than returning an empty result. For example, Address lookup reports that no address history is available, and Business details reports that no search results were found. ## Immediate and pending results * **Immediate**: most checks query their source in real time and return the result straight away, usually within seconds. Product pages show these as *near real-time*. * **Pending**: some checks depend on a third party with its own turnaround, such as SAPS for criminal records or Umalusi and institutions for qualifications. The check is accepted with a pending status and the result is available when the source responds, anywhere from hours to weeks. In the portal you see the status change; through the API you retrieve the result when it is ready. See [Data sources and turnaround](/product/overview/how-it-works/data-sources.md) for typical turnaround times. --- # 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/results-and-outcomes.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.