Re-authenticates users in transactions post registration, allowing the authentication methods to vary by the desired experience and flow criticality.
How it works
Smart revalidation confirms that whoever makes a transaction is the same user who registered before. Unico's engine runs two assessments: one with network intelligence, which analyzes the user's behavior, and one on session security. Based on them, it sets the friction needed: a silent validation, with no action from the user, or a facial biometric (facematch plus liveness) when the risk calls for it.
You choose who operates the authentication experience. In both methods, the engine is the same.
| Method 1: Smart revalidation, default mode | Method 2: Smart revalidation, silent mode | |
|---|---|---|
| How it works | Unico operates the authentication experience: it runs the engine and, when needed, the facial biometric. You receive only the final answer. | The engine tells whether Unico is confident it is the expected user, without asking anything from them. You operate the authentication experience, and your risk tree decides the next step. |
| You receive | YES or NO | YES or NO |
| Who operates the authentication experience | Unico | You |
| Step-up | Run by Unico. | We recommend Unico facial biometrics: besides having the best liveness on the market, it feeds the engine, which sustains Unico's standard accuracy and unlocks more silent validations. |
Method 1: default mode
Method 2: silent mode
What this product solves
Use this product when:
- Periodic revalidation (e.g., passwordless login, weekly re-check).
- Financial transfers
- Account management (e.g., password or limit changes)
- Service subscriptions
- New device registration
- Financial operations (investments, loans, cashout), among others.
Capabilities involved
Single adaptive capability:
| Capability | Requirement | Role in the flow |
|---|---|---|
| Smart Revalidation | Required | Orchestrates metadata and biometric data adaptively to verify whether the user matches the reference process. |
Prerequisites
- Bearer token — see Authentication.
- Sandbox credentials — see Environments.
- SDK or Web component installed — only for Web and SDK integrations. See SDKs and Tools.
- Reference biometric — the user must have previously completed an onboarding or biometric registration process. Pass it via the
referencesarray in Create Process: each item requiresreferenceType(REFERENCE_TYPE_PROCESS_ID,REFERENCE_TYPE_IMAGE_BASE64orREFERENCE_TYPE_HUMAN_TOKEN) andreferenceContent(the process UUID, base64-encoded image orhumanTokenreturned by Human Token). useCasevalue — required when creating the process. See Smart Revalidation for the full list of valid values and their behavior.
Step-by-step implementation
- Native
- Web
- 🇧🇷 ApiOnly (Native SDK + API)
Integration via native SDK — capture runs inside your app using the Unico SDK for Android, iOS or Flutter.
- Install the SDK — add the Unico SDK dependency for your platform. See the setup guide for Android, iOS or Flutter.
- Create a process — call Create Process with the appropriate
flowvalue and the user's identifier. Use the returnedtokento initialize the SDK. - Start the capture — the SDK renders the camera UI and performs liveness detection on-device, returning the captured payload.
- Query the result — call Get Process to retrieve the capability results.
- Apply business rules — evaluate the response fields to approve, deny or escalate.
Integration via iFrame, Redirect or Native — Unico hosts the capture UI, and you receive the result via polling.
- Create a process — call Create Process with the appropriate
flowvalue and the user's identifier. The response includes auserRedirectUrl. - Redirect the user — send the user to
userRedirectUrl. Unico renders the capture journey. OrwebAppTokenin native apps. - User completes the journey — after capture, the user is redirected back to your
callbackUri. - Query the result — call Get Process to retrieve the capability results.
- Apply business rules — evaluate the response fields to approve, deny or escalate.
For apps on ApiOnly (Native SDK + API): your app captures with the Unico native SDK and your backend creates the process with Create Process. Smart Revalidation works on this integration without reintegrating. The only change is sending the reference process when the camera opens.
- Update the SDK — Android SDK 6.13.0 or later, iOS SDK 3.4.0 or later, or Flutter plugin 4.65.0 or later. These versions open the camera with
idSmartOptions. See the Capture API for Android, iOS or Flutter. - Open the camera with the reference process — pass
idSmartOptionswithreferenceProcessIdanduseCase.referenceProcessIdis the id of an earlier, concluded process of the same user, created by your account (for example, the user's Onboarding). Use theidthat the Unico API returned when that process was created.useCasetakes one of the values listed in Smart Revalidation. Without a reference process, the SDK runs your current journey, without Smart Revalidation. - Receive the JWT — the SDK returns the result in the same success callback as today:
- Approved by silent authentication: the camera does not open, and the JWT has no image. The image preview returned with it comes empty.
- Escalated to facial biometry: the SDK opens the camera and the JWT carries the selfie, as today.
- Create the process — your backend sends the JWT in
imageBase64to Create Process, with the sameAPIKEY. The response includes the Smart Revalidation result. - Apply business rules — evaluate the response fields to approve, deny or escalate.
Unico enables Smart Revalidation on your SDK Key and on your APIKEY. If your SDK Key is not enabled, the SDK ignores the reference process and runs your current journey.

