Authentication
Authentication compares a newly-uploaded Selfie and Facemap to an existing Facemap that is already associated with the account to verify that the current end user is the same person as the known identity.
For a detailed description see Authentication Workflow.
Dependencies
-
An existing Facemap must already be associated with the account.
If your data retention policies remove existing credentials you have the option of using Authentication On-Premises. -
The Liveness check must pass before the workflow can proceed to Authentication.
Supported Credentials
Decision Details Labels
Decision Type |
Label |
Description |
---|---|---|
NOT_EXECUTED |
PRECONDITION_NOT_FULFILLED |
Required data from another capability is not available. |
NOT_EXECUTED |
TECHNICAL_ERROR |
A technical error prevented the capability from executing. |
PASSED |
OK |
The end user is the same person who previously uploaded credentials under the same account. |
REJECTED |
FAILED |
The end user is not the same person who previously uploaded credentials under the same account. |
WARNING |
FACE_UNCLEAR_QUALITY |
The detected face does not meet the required quality standards for reliable processing. We recommend allowing the end-user another attempt (up to 3 attempts) by the customer to initialize another authentication transaction. This parameter will be returned starting March 31, 2025. |
Data
Key |
Type |
Description |
---|---|---|
type |
string |
The service that is used. Possible values:
|
"validFaceMapForAuthentication"
value, which is the href to the facemap used for comparison.