Capabilities

Reference, not entry point

This section is a technical reference. If you're starting an integration, begin with Use Cases — they describe the business problem you want to solve. Capabilities are consulted from there, when you need to understand in detail what each block does and how it responds.

How capabilities, flows, and use cases relate

Use case  →  Flow  →  Capabilities
(the problem)   (the recipe)   (the ingredients)

• Use case is the business problem: "validate the identity of a new customer in Brazil", "confirm holder identity on a sensitive transaction".
• Flow is the pre-composed combination of capabilities that solves that use case. It's the exact value you send in the flow field of POST /v1/process.
• Capability is the atomic block — each with its own goal, inputs, and possible responses. This is its reference page.

For the full table of which flows exist and which capabilities each one combines, see Available flows.

Capability catalog

Capability	What it solves	Available on
Liveness	Verifies that the user is real and alive at the moment of selfie capture.	SDK, Web, API
Identity Verification	Verifies that the captured face belongs to the holder of the identification document.	SDK, Web, API
Risk Fraud Classification	Complements identity verification with behavioral analysis to detect fraud risk.	SDK, Web, API
Risk Score	Probabilistic fraud score, used together with Identity Verification when the result is "inconclusive".	SDK, Web, API Brazil only
1:1 Validation	Confirms the current face is the same one used in a reference process.	SDK, Web, API
Smart Revalidation	Orchestrates multiple identity verification methods adaptively, choosing the least-friction approach for each transaction based on available signals.	Web, SDK
Document Capture & Reuse	Requests, stores, and reuses documents. Reduces friction in journeys with document capture.	SDK, Web, API
Serpro Similarity Return	Comparison against the Serpro database — specific to payroll loans (INSS) and similar operations.	SDK, Web, API Brazil only
Age Verification	Determines whether the person in front of the camera meets the minimum required age, based on biometric analysis.	SDK, Web, API
Step-up Authentication	Detects whether a face is already linked to another account in the operator's base via 1:N biometric search.	API

Integration surfaces

Web delivers the journey via iFrame or Redirect (component managed by Unico). SDK delivers capture via native SDK (Android, iOS, Flutter). API is the headless integration, without the Unico SDK, with your own front-end (Capture Standard) or direct base64 image upload.

Anatomy of each capability page

Every capability page follows the same format, to make cross-referencing easier:

1. What it does — the capability's goal in a sentence.
2. Inputs — what needs to be sent to use it.
3. Possible responses — every possible return value and what each one means.
4. Availability — supported surfaces (SDK, Web, API).
5. Valid combinations — in which flows from the catalog this capability appears.
6. Use cases that use this capability — links back to the Use Cases axis.

What's next

• Want to know which flow uses which combination of capabilities? → Available flows
• Want to browse the catalog of problems the platform solves? → Use Cases