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

# Ways to use Fraudcheck

Run checks in the portal, through the API, or in a digital onboarding journey.

## The portal

The client portal is a web application for running checks, reading results and managing your account. It needs no integration work. [Log in to the portal](https://portal.fraudcheckonline.co.za/login), or see [Using the portal](/product/administration/administration/portal.md).

## The API

Run checks from your own systems. The API is split into two services, each with its own reference:

* [Consumer API](https://developer.fraudcheck.co.za/consumer-service): checks on individuals.
* [Commercial API](https://developer.fraudcheck.co.za/commercial-service): checks on companies, trusts and other legal entities.

Each product page says which channels offer it and links to its API page.

## Digital onboarding

Some identity checks run as a capture journey for the person being checked: a hosted flow on our domain that you link to, or an embedded flow inside your own app. The person enters their details, captures a document or selfie, and you receive the result. See [Digital onboarding](/product/platform/platform/digital-onboarding.md) and [Identity Verification - Enhanced with Liveness](/product/products/verification/identity/digital-onboarding.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/overview/how-it-works/channels.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.