Smart revalidation

Re-authenticates users in transactions post registration, allowing the authentication methods to vary by the desired experience and flow criticality.

What this use case solves

Smart revalidation addresses the challenge of re-authenticating users with the least possible friction, by orchestrating multiple identity verification methods adaptively — choosing the most appropriate method for the risk level of each transaction. Instead of always requiring a full biometric capture, it combines metadata and/or passkeys with existing biometric data (if desired).

The minimum friction level can be set by picking the useCase, based on the criticality level, it is possible to set the minimum friction to be silent authentication, passkey or simply just have facial biometry as a challenge. Once picked, Unico will orchestrate the lowest friction technology possible, always guaranteeing the same level of safety of a facial biometry.

Use this use case 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.

Do not use this use case when:

• The transaction requires explicit biometric capture every time → look at the other transactional use cases.

Capabilities involved

Single adaptive capability:

Smart Revalidation

Capability	Requirement	Role in the flow
Smart Revalidation	Required	Orchestrates metadata, passkeys 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 references array in Create Process: each item requires referenceType (REFERENCE_TYPE_PROCESS_ID or REFERENCE_TYPE_IMAGE_BASE64) and referenceContent (the process UUID or base64-encoded image).
• useCase value — required when creating the process. See Smart Revalidation for the full list of valid values and their behavior.

Step-by-step implementation

Native

Integration via native SDK — capture runs inside your app using the Unico SDK for Android, iOS or Flutter.

1. Install the SDK — add the Unico SDK dependency for your platform. See the setup guide for Android, iOS or Flutter.
2. Create a process — call Create Process with the appropriate flow value and the user's identifier. Use the returned token to initialize the SDK.
3. Start the capture — the SDK renders the camera UI and performs liveness detection on-device, returning the captured payload.
4. Query the result — call Get Process to retrieve the capability results.
5. Apply business rules — evaluate the response fields to approve, deny or escalate.

Android

Native Android SDK for in-app capture.

View overview

iOS

Native iOS SDK for in-app capture.

View overview

Flutter

Cross-platform Flutter SDK for in-app capture.

View overview

Web

Integration via iFrame, Redirect or Native — Unico hosts the capture UI, and you receive the result via polling.

1. Create a process — call Create Process with the appropriate flow value and the user's identifier. The response includes a userRedirectUrl.
2. Redirect the user — send the user to userRedirectUrl. Unico renders the capture journey. Or webAppToken in native apps.
3. User completes the journey — after capture, the user is redirected back to your callbackUri.
4. Query the result — call Get Process to retrieve the capability results.
5. Apply business rules — evaluate the response fields to approve, deny or escalate.

Web

Quick integration via browser, no installation needed.

View overview