> ## Documentation Index
> Fetch the complete documentation index at: https://docs.idmetagroup.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Account Ownership Validation via Advanced Face Compare
> Learn how to validate account ownership by comparing a newly captured selfie against the original onboarding selfie using Company Unique Identifier (CUI) and Source Company Unique Identifier (SCUI).
## Overview
The **Advanced Face Compare** feature allows you to validate that the person performing a sensitive action, such as a withdrawal or account recovery request, is the same person who previously completed onboarding on your platform.
This is done by comparing:
* the **selfie captured during the current Biometrics Verification session**, and
* the **selfie captured during the user's original onboarding process**
This feature is useful for platforms that need an added layer of identity assurance before allowing high-risk actions.
This feature is available upon request and is not enabled on your account by default. Please contact your support administrator to have it activated.
***
## Why this feature is needed
Many platforms require users to complete eKYC during onboarding. This usually includes:
* Document Verification
* Biometrics Verification
* Face Compare
During the onboarding process, a selfie is captured as part of Biometrics Verification.
Later, when the same user performs a sensitive action such as:
* withdrawing funds
* changing important account information
* linking a bank account
* recovering account access
* approving a high-risk transaction
you may want to confirm that the person performing the action is the original account owner.
The Advanced Face Compare feature makes this possible by retrieving the user's original onboarding selfie and comparing it with a newly captured selfie.
Use this feature whenever you need to validate that the current user is the same person who originally completed onboarding on your platform.
***
## How it works
This feature works by linking a user's onboarding verification result to a unique identifier from your platform.
### 1. Pass your unique identifier during Onboarding Trust Flow
During the onboarding trust flow that includes biometrics verifications, include the URL parameter below into the Direct Link URL:
`cui`
Example:
```text theme={null}
&cui=12345
```
The `cui` (Company Unique Identifier) value should be a unique reference from your platform that can be used to identify the user or account. For example:
* account ID
* user ID
* username
Once provided, this value will be stored in the Trust Validation Result for that verification record. This allows the Trust Validation Result to be linked back to the corresponding user or account record in your system.
Do not enable "Perform Advance Face Compare" in your Biometrics Verification tool settings in this Trust Flow
Example Onboarding Trust Flow with Biometrics Verification
URL Parameter is added into Direct Link URL
### 2. Enable Advanced Face Compare and pass the source identifier in Account Ownership Validation Trust Flow
In your Account Ownership Validation Trust Flow (separate from your Onboarding Trust Flow), go to the **Biometrics Verification Tool Settings** and enable:
`Perform Advance Face Compare`
Then include the following URL parameter into the Direct Link URL:
`scui`
Example:
```text theme={null}
&scui=12345
```
This stands for **Source Company Unique Identifier**. The `scui` value must match the original `cui` value passed during onboarding.
The system will use this value to locate the matching Trust Validation Result from the Onboarding Trust Flow, extract the selfie captured at that time as the **source image**, and compare it against the selfie from the current session as the **target image**. A **similarity score** is then returned to help determine whether both selfies belong to the same person.
***
## End-to-end flow
### Onboarding flow
During onboarding, the user completes your normal eKYC process.
This may include:
* Document Verification
* Biometrics Verification
* Face Compare
At this stage, include the `cui` parameter in the Direct Link URL.
```text theme={null}
https://your-direct-link-url.com?...&cui=15551234
```
This stores your platform's unique identifier together with the Trust Validation Result.
### Account Ownership Validation Flow
Later, when the user wants to perform a sensitive action and requires ownership validation, initiate a new verification flow that includes Biometrics Verification with **Perform Advance Face Compare** enabled.
In the Direct Link URL, include the `scui` parameter:
```text theme={null}
https://your-direct-link-url.com?...&scui=15551234
```
The platform will then:
1. search for the previous Trust Validation Result with matching `cui`
2. retrieve the selfie from that earlier verification
3. capture a new selfie from the current session
4. compare both selfies
5. return a similarity score
This helps validate that the current user is the same person who completed onboarding.
The `scui` value must match the original `cui` value exactly. If it does not match, the platform will not be able to retrieve the source selfie from the earlier Trust Validation Result.
***
## URL parameters
### `cui`
**Meaning:** Company Unique Identifier
**Purpose:** Used during the original verification flow to store your platform's unique identifier in the Trust Validation Result.
**Examples:**
* `15551234`
* `johnsmith_01`
* `ACC-100245`
* `ea23-29ousS-qweq`
### `scui`
**Meaning:** Source Company Unique Identifier
**Purpose:** Used during a later verification flow to locate the earlier Trust Validation Result that contains the source selfie.
**Important:** The `scui` value should match the `cui` value that was used in the original onboarding flow.
***
## Result behavior
When a matching prior Trust Validation Result is found through `scui`, the system will:
* retrieve the source selfie from the earlier process
* compare it against the current Biometrics Verification selfie
* generate a similarity score
* include a link to the original onboarding Trust Validation Result, so you can trace the source verification that was used for comparison
This score can then be used by your platform to help determine whether the current user matches the original verified identity.
***
## Recommended use cases
This feature can be used in any scenario where you need to confirm that the user performing an action is the original account owner.
Common examples include:
* withdrawals
* bank account linking
* account recovery
* profile ownership validation
* high-risk account changes
* transaction confirmation for sensitive actions
***
## Summary
The Advanced Face Compare feature helps validate account ownership by comparing:
* a selfie captured during the current verification flow, and
* the selfie captured during the user's original onboarding process
To use this feature:
1. pass `cui` during onboarding to store your unique identifier in the Trust Validation Result
2. enable **Perform Advance Face Compare** in Biometrics Verification Tool Settings
3. pass `scui` during the later verification flow to retrieve the original onboarding selfie
4. use the returned similarity score to help determine whether the same person is performing the action
This provides a simple and effective way to strengthen identity validation for sensitive account activities.