> 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/document-with-liveness.md). # Identity Verification - Document with Liveness Authenticates an identity document and confirms it belongs to the person presenting it, using a live selfie. Authenticates a physical identity document and confirms it belongs to the person presenting it, using a live selfie that is liveness-checked and face-matched against the portrait on the document. ## How it works The document goes through an authentication pipeline: classification, reading of the printed data, barcode or machine-readable zone reading, cross-field validation and security-feature checks. A liveness check then runs on the captured selfie, followed by a face match against the portrait extracted from the document. It is available through two delivery methods: * **Hosted flow**: the person is redirected to a fully managed capture experience on our domain. No SDK integration is needed. * **Embedded flow**: the same capture technology runs inside your own app or site, so there is no visible hand-off to another domain. Both methods support your branding, and let the person start on one device and finish capture on another by QR code, SMS or email. You can follow a transaction's progress and receive the result when it is ready. **Candidate user flow**

Personal details form requesting first name, last name, ID number and nationality

Screen prompting the candidate to fit their identity document inside the frame

Liveness capture screen prompting the candidate to hold still and fill the oval

Completion screen confirming that the candidate's information has been received

## What it returns The document authenticity result, a liveness outcome, a face match between the selfie and the document portrait, and the transaction's final status. ## Inputs required A live capture session in which the person photographs their identity document and then takes a liveness selfie, through the hosted or embedded flow. ## Data source The identity document itself (its security features and the data printed and encoded on it) 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 session creation, capture options and result retrieval, see the [API reference](https://developer.fraudcheck.co.za/consumer-service/identity/identity-verification-document-with-liveness). ## Outcomes * **Pass**: the document is authentic, the liveness check passed and the selfie matched the document portrait. * **Review**: the result requires manual review. * **Fail**: one or more checks did not pass. The result includes reasons for the failure. ## Turnaround Near real-time once the person completes capture. ## When to use it High-risk scenarios, onboarding, KYC, or any flow that needs proof that the presenter is the document's rightful holder, not just that the document 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/document-with-liveness.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.