> For the complete documentation index, see [llms.txt](https://docs.uaepass.ae/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uaepass.ae/facial-biometric-transactions-confirmation/generic-implementation-guidelines.md).

# Generic Implementation Guidelines

The following implementation guidelines must be adhered to when integrating this feature:

* The SP will be provided with separate **client credentials** dedicated to the Facial Biometric Transaction Confirmation feature.
* This feature is available to **Verified Residents** and **Verified Visitors** of **UAE PASS**.
* The service provider must ensure that the correct user identifier (EID/Mobile/Email) is passed in the [Authorization request](/facial-biometric-transactions-confirmation/steps-to-integrate.md) as username parameter to ensure that the Facial Biometric TC request is triggered for the correct user.&#x20;
* Upon successful completion of the request and receipt of a successful response from UAE PASS, the service provider must ensure that it is the intended user who has completed the Facial Biometric TC feature.

This can be achieved by following the steps below:

1. Invoke the Authorization request and obtain the authorization code after successful Facial Biometric TC confirmation from the user.
2. Invoke the UAE PASS token request and obtain the access token.
3. Invoke the User Info API and retrieve the user information.
4. Compare the user attributes received in the User Info response against the User Info response received during UAE PASS Authentication session.
5. Strongly recommended to validate against the Sub and Emirates ID values. Service provider must make sure that this validation is performed against the **already logged in user's information**.
6. Once the intended user is verified, the service provider can proceed with the transaction flow.
7. If the validation is failed, Service provider must break the user journey.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uaepass.ae/facial-biometric-transactions-confirmation/generic-implementation-guidelines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
