Identity Verification

MarkdownChatGPTClaude

This capability verifies whether the person in the transaction is who they claim to be.

What it does

Uses Unico's identity base and additional signals to return a verdict on whether the face of the transaction (captured or provided) belongs to the holder of the respective government identifier.

Inputs

• A capture session opened via POST /v1/process with a flow that includes Identity Verification, or a base64 image submitted via POST /processes/v1.
• The user's government identifier (CPF, in Brazil).

Possible responses

Response	API contract	Web & Native contract	Meaning
YES	yes	AUTHENTICATION_RESULT_POSITIVE	The face belongs to the holder of the provided government identifier.
NO	no	AUTHENTICATION_RESULT_NEGATIVE	The face does NOT belong to the holder of the provided government identifier.
INCONCLUSIVE	inconclusive	AUTHENTICATION_RESULT_INCONCLUSIVE	Insufficient evidence to decide.

The API contract (POST /processes/v1) returns lowercase strings in idCloud.result. The Web & Native contract (GET /client/v1/process/{id}) returns full enum strings in authenticationInfo.authenticationResult. See Get Process for the full enum table.

In Mexico, the result can come with a RENAPO Verification block, which is a separate answer.

Inconclusive response handling

When inconclusive, Risk Score can provide a probabilistic answer instead of a binary verdict.

When the result is INCONCLUSIVE, you can orchestrate with the Risk Score capability to obtain a probabilistic answer and base the decision on a score, not on a binary verdict.

Availability

Surface	Supported
SDK (Android, iOS, Flutter)	✅
Web (iFrame, Redirect)	✅
API (headless, no SDK)	✅