Skip to main content
Face Identifier

Face Identifier is designed for scenarios where there is no government-issued document relationship — situations where customers want to avoid sharing document numbers for privacy reasons. Its core function is to create a unique identity for each face from a single selfie submission.

This allows you to:

  • Detect recurring users and prevent duplicate accounts — recognize whether the same person is returning or attempting to create multiple accounts, ensuring consistent identity recognition without official documents.
  • Integrate via Web, Native, or API — using only the selfie image as input, with no additional document data required.
  • Combine with other signals — add Face Identifier alongside other capabilities as needed.

What it does

From the captured selfie, Face Identifier generates a stable, opaque biometric identifier (personId) that uniquely represents that face. The user does not declare any identifier — identity is the output of the call, not the input. On every successful match, the response returns the same personId, allowing the same user to be recognized in future processes.

Inputs

The selfie is captured by the SDK or the Web journey. For headless API integration, the image is sent as imagebase64 in the body of POST /v1/process with flow=idface. Do not include subject.code — Face Identifier returns the personId in the response.

SDK required for quality capture

To ensure the image sent via API meets biometric requirements, use the Unico SDK for your platform or follow the Capture Standard. Face Identifier does not accept arbitrary images without capture quality control.

Possible responses

idFace.resultMeaning
FOUNDIdentity confirmed. personId is returned and populated.
NOT_FOUNDIdentity not confirmed. personId will be absent.

Response example

{
"id": "1c1fc38b-7e98-4f9a-a04d-7a4a8b29d2c1",
"status": 3,
"idFace": {
"personId": "a1b2c3d4e5f67890a1b2c3d4e5f67890a1b2c3d4e5f67890a1b2c3d4e5f67890",
"result": "FOUND"
}
}

personId is a stable, opaque identifier — the same user will always resolve to the same value. Store it alongside your user record to recognize the same person on subsequent Face Identifier calls.

Availability

SurfaceSupported
SDK (Android, iOS, Flutter)
Web (iFrame, Redirect)
API (headless, no SDK)