> 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/documents/id-document-authentication.md). # Identity document authentication Confirms an identity document is genuine and unaltered, and extracts its details. No selfie. A document-only check that confirms a passport, driver's licence, national ID or other travel document is genuine and unaltered, and extracts the personal details in it. No selfie is captured, so it does not confirm that the presenter is the document's rightful holder. For that, use [Identity Verification - Document with Liveness](/product/products/verification/identity/document-with-liveness.md). ## How it works In the portal, you upload copies of the identity document (front and back for two-sided documents) with the holder's name and ID number. The document is analysed for its security features and its data is extracted. Checks include classification, reading of the printed data, barcode or machine-readable zone reading, cross-field validation and security-feature checks. The result is shown in the portal and can be downloaded as a report. ## What it returns A verification outcome; the document type (passport, driver's licence or national ID); extracted details (name, ID number, date of birth, gender, nationality, issuing country, issue and expiry dates, and address where present); whether the ID number is valid; and whether the holder is over 18. ## Inputs required The holder's ID or passport number, first name and last name, and a clear full-colour image of the front and back of the document (JPEG, PNG or PDF; at least 300 DPI; up to 5 MB). ## Data source The identity document itself: its security features and the data printed and encoded on it. ## 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 only. The document copies are uploaded by your user in the portal; there is no capture journey for the person being checked. ## Outcomes * **Accepted**: the document passed authentication. * **Rejected**: the document failed authentication. * **Refer**: the result needs a human look. Each outcome comes with a numeric result code, shown in the report. ## Turnaround Near real-time, typically 5–30 seconds after the document is uploaded. ## When to use it * Verifying a passport, driver's licence, national ID or other travel document during onboarding. * Detecting fraudulent or tampered identity documents. * Confirming a document is still valid and that the holder is over 18. * Reading name, ID number, date of birth and other details from the document instead of capturing them by hand. * Where confirming the document is genuine is enough, because you bind identity elsewhere in your flow or your risk profile does not need it. --- # 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/documents/id-document-authentication.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.