> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/faqs.md).

# FAQs

<details>

<summary><strong>How do we handle Aadhaar verification failures?</strong></summary>

The workflow fails due to a Know Your Customer (KYC) failure. You can see the reason in the node's Instance results and in the Sessions dashboard in AdminX, along with the individual match indicators (name, date of birth, PIN code, face) that show which check didn't match.

</details>

<details>

<summary><strong>What is the face-match threshold, and is it configurable?</strong></summary>

The face match threshold is 0.7. A `face_match_confidence` score above 0.7 is accepted. Users and admins can't configure this threshold today because it is part of the workflow that runs on the root tenant.

</details>

<details>

<summary><strong>Where does the liveness check get configured?</strong></summary>

Liveness for the selfie capture step is configured at the root tenant level, not per workflow or per admin.

</details>

<details>

<summary><strong>What happens if a user doesn't have a DigiLocker account?</strong></summary>

The user can create one during the redirect. On the DigiLocker screen, they select **Try another way**, which takes them to DigiLocker's account-creation flow.

</details>

<details>

<summary><strong>What happens if a user presents someone else's face during the selfie step?</strong></summary>

The node still completes because it matches the name, date of birth, and PIN code independently of the face. Only the face match fails: `face_match_result` returns `false` with a `face_match_confidence` below the 0.7 threshold; the other match indicators (name, date of birth, address/PIN) can still return `true` and the overall outcome is **Verification Failed**.

</details>


---

# 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.1kosmos.com/identity-verification/faqs.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.