[Legacy] Getting Started With Face Authentication

Warning

This method of Face Authentication is being deprecated in favor of an updated method that uses a Face Authentication module within Workflows and Flows. This change allows for a higher level of security and configurability when authenticating users.

Key dates:

• End of Support (EoS): October 1, 2026
• End of Life (EoL) / Retirement: April 1, 2027

We recommend completing your migration by January 1, 2027 to avoid any last-minute issues or service disruptions.

Documentation for the new method of Face Authentication can be found here:

• Overview
• Module configuration
• Face Authentication webhook

Face authentication can provide an added level of security for organizations, applications, or even higher-level sections of application. For example, you could grant access to specific functionality within your application using face authentication. This would ensure the person requesting access has a valid, registered Incode Identity.

How the face authentication process works

You can implement Incode face authentication by using either the Web or Mobile SDKs to enable a face recognition UI that asks the user for a selfie. This selfie image is then used for comparison using 1:N or 1:1 strategies.

The basic face authentication steps are:

1. Initialize the Incode SDK.
2. Run the method.
3. Based on the face capture, check to see if the user has a registered Incode Identity.
4. If yes, validate the authentication using the omni/authentication/verify endpoint of the Incode Omni API.
5. In your application back end, check whether Incode verified the authentication, and grant or deny access to the user.

The following diagram can help you visualize these steps.