> For the complete documentation index, see [llms.txt](https://docs.elkyc.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elkyc.com/home/build-verification-flows/verification-steps/liveness.md). # Liveness The Liveness step is designed to verify the presence of a live person during the verification process. * Add `Liveness Check` step into the flow canvas at the appropriate position in the flow. * Click on `Liveness Check` to open its configuration options:


Number of Attempts	Define the maximum number of attempts allowed for the liveness check. The limit is set to 5 attempts.
One-shot Liveness	A quick, single-step verification process.
3D Liveness	Advanced verification using 3D imaging technology.
Custom 3D Liveness	Combine various actions (e.g., eye movement, smile) for a more robust check.
Style Customization	Customize the UI to match your brand's look and feel.
Verification Validity Period	This setting defines how long a successful verification result remains valid. Enforce re-verification after a defined time window for security or compliance needs.

--- # 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.elkyc.com/home/build-verification-flows/verification-steps/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.