> 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/verification/identity/digital-onboarding.md).

# Identity Verification - Enhanced with Liveness

Binds an identity to the person presenting it with a live selfie matched against the photo on record, with no document needed.

Confirms a South African identity is real and binds it to the person presenting it, without needing a physical document. The person supplies their name and ID number and takes a live selfie, which is matched against a photo held on record.

## How it works

The flow runs in three steps: the person's details are captured, a liveness selfie is captured, and the selfie is matched against a photo retrieved through a registry lookup. The registry lookup runs in one of three modes:

* **On file only**: checks on-file data only. If no record is found, the result is Not found alongside the liveness result.
* **Online only**: always queries live Department of Home Affairs data, and falls back to on-file data if the live source is unavailable.
* **Auto**: checks on-file data first and escalates to live data only if no record is found.

It is available through three delivery methods. The **hosted flow** redirects the person to a fully managed capture experience on our domain, with no SDK required. The **embedded flow** runs the same capture inside your own app or site. **Input only** skips live capture: you submit the person's details and an existing selfie, so no liveness check runs, only the face match. Hosted and embedded flows support your branding and cross-device hand-off by QR code, SMS or email.

**Candidate user flow**

<figure><img src="https://2837330194-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHmg0BqAOfNqlLWgnmNnd%2Fuploads%2Fgit-blob-71bebdf323378853f41eb62c9de1b50024a7a83d%2Fliveness-01-personal-details.png?alt=media" alt="Personal details form requesting first name, last name and ID number" width="240"><figcaption><p>Personal details form requesting first name, last name and ID number</p></figcaption></figure>

<figure><img src="https://2837330194-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHmg0BqAOfNqlLWgnmNnd%2Fuploads%2Fgit-blob-40461df07802ca51aa094560516b559c5476a292%2Fdwl-03-liveness-capture.png?alt=media" alt="Liveness capture screen prompting the candidate to hold still and fill the oval" width="240"><figcaption><p>Liveness capture screen prompting the candidate to hold still and fill the oval</p></figcaption></figure>

<figure><img src="https://2837330194-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHmg0BqAOfNqlLWgnmNnd%2Fuploads%2Fgit-blob-fa314b560b2dc71c33b590f33888946aac118a00%2Fdwl-04-completion.png?alt=media" alt="Completion screen confirming that the candidate&#x27;s information has been received" width="240"><figcaption><p>Completion screen confirming that the candidate's information has been received</p></figcaption></figure>

## What it returns

An overall outcome built from four checks: whether the selfie is live, whether a matching record was found, whether the submitted name matches the record within a configurable tolerance, and whether the selfie matches the photo on record.

## Inputs required

First name, last name and ID number, captured on a screen we provide or passed in by your system so the person only sees the selfie step, plus a selfie captured live (or submitted directly through the input-only method).

## Data source

Department of Home Affairs records, live or on file depending on the mode, and a live selfie.

## Consent and permissible purpose

You must obtain the data subject's consent before running this check, and confirm on each request that you have it. You keep the proof of consent; Fraudcheck records that you confirmed it. See [Consent and permissible use](/product/overview/how-it-works/consent.md).

## Channels

Portal and API. For request and response detail, see the [API reference](https://developer.fraudcheck.co.za/consumer-service/identity/biometric-identity-verification).

## Outcomes

* **Accept**: the identity was found, the name matched, liveness passed and the selfie matched the official photograph.
* **Reject**: the name, liveness check or face match did not pass.
* **Review**: the liveness or face-match result is inconclusive and needs a human look.
* **Fail**: no identity record was found, so no selfie capture was started, or the source could not be reached.

While the person has not yet completed the selfie capture, the result shows as **Pending**. Pending is a status, not a final outcome.

## Turnaround

Near real-time once the person completes capture. Results can be pushed to your system when ready.

## When to use it

High-risk scenarios, onboarding, KYC, or any flow that needs proof that the presenter is the identity's rightful holder, not just that the identity is genuine.


---

# 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/verification/identity/digital-onboarding.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.