Smart Revalidation
Re-authenticates users in transactions post registration, allowing the authentication methods to vary by the desired experience and flow criticality.
What it does
Applies a two-tier orchestration engine that dynamically routes each transaction through the most appropriate authentication method based on real-time risk signals:
- Metadata Engine — analyzes contextual and behavioral data against the user's historical profile, and also the session risk, to make sure the online session is secure. An AI-based adaptive engine scores device metadata, behavioral signals and the user's transaction history in the background to calculate a real-time risk level and decide which authentication tier to trigger. When the analysis is positive, the outcome is Silent Authentication: Unico revalidates the user silently, with zero friction, based only on metadata and historical analysis.
- Facial Biometric — used when the engine cannot validate silently with the same level of security, or when the client wants facial biometrics for any reason. Runs facematch against the user's registered biometric, together with liveness detection.
Operation modes
Both modes use the same engine. What changes is who operates the authentication experience.
| Mode | Who operates | What happens |
|---|---|---|
| Smart revalidation, default mode | Unico | Unico runs the authentication on its side, including facial biometrics when needed, and delivers the final result to you. |
| Smart revalidation, silent mode | You | Unico delivers only the engine's recommendation. You operate the authentication experience and decide the next step. For step-up, we recommend Unico facial biometrics. |
In silent mode, a NO ends the process. To run the step-up with Unico facial biometrics, create a new process, for example with a USE_CASE_CRITICAL_* value.
See both flows in full on the solution page.
Possible responses
| Response | Smart revalidation, default mode | Smart revalidation, silent mode |
|---|---|---|
YES | This is the expected user. | Unico is confident, silently, that this is the expected user. |
NO | This is not the expected user. | Unico is not confident, silently, that this is the expected user. |
The useCase parameter
When creating a process, the useCase field controls how the orchestration engine routes the transaction. It combines two dimensions:
- Flow type — the business context of the transaction.
- Criticality level — the minimum friction baseline, restricting which authentication tiers are available.
Flow types
| Flow type | Description |
|---|---|
LOGIN | Standard access and high-frequency validation (e.g., passwordless login, gym check-ins). |
ACC_MANAGEMENT | Structural account actions: profile updates, credential changes, device swaps. |
FIN_TRANSACTIONS | Monetary movements: transfers, payments, purchases, investment orders. |
FIN_SERVICES | Non-monetary financial actions: credit applications, loan releases, card blocking. |
CUSTOM | Custom workflows that do not map to standard categories. |
Criticality levels
| Criticality | Authentication tiers available |
|---|---|
EXPERIENCE (default) | All tiers — engine maximizes silent authentication. |
SILENT | Silent Authentication only. Unico delivers the engine's recommendation and does not trigger facial biometrics. The client operates the authentication experience. |
CRITICAL | Facial Biometric only. |
SENSITIVE (deprecated) | Still accepted for existing integrations, without Silent Authentication. New integrations use CRITICAL. |
useCase enum values
| Category | Enum value | Description |
|---|---|---|
| Experience | USE_CASE_LOGIN | Optimizes for seamless, zero-friction return flows. |
| Experience | USE_CASE_ACC_MANAGEMENT | Dynamic baseline for standard profile actions. |
| Experience | USE_CASE_FIN_TRANSACTIONS | ML-driven fraud check for payments. |
| Experience | USE_CASE_CUSTOM | Flexible orchestration for tailored business logic. |
| Silent | USE_CASE_SILENT_LOGIN | Delivers the engine's recommendation, in silent mode, for return flows to the client's platform, such as passwordless login and check-in. |
| Silent | USE_CASE_SILENT_ACC_MANAGEMENT | Delivers the engine's recommendation, in silent mode, for account profile changes, such as password change, new device and address update. |
| Silent | USE_CASE_SILENT_FIN_TRANSACTIONS | Delivers the engine's recommendation, in silent mode, for financial transactions, such as PIX/TED (Brazil), Venmo/Zelle (US) and cash withdrawal. |
| Silent | USE_CASE_SILENT_FIN_SERVICES | Delivers the engine's recommendation, in silent mode, for financial service applications, such as contracts and loans. |
| Silent | USE_CASE_SILENT_CUSTOM | Delivers the engine's recommendation, in silent mode, for flows other than those mentioned above. |
| Critical | USE_CASE_CRITICAL_ACC_MANAGEMENT | Facial Biometric only — account recovery. |
| Critical | USE_CASE_CRITICAL_FIN_TRANSACTIONS | Facial Biometric only — high-value cashouts. |
| Critical | USE_CASE_CRITICAL_FIN_SERVICES | Facial Biometric only — contracts and loans. |
| Critical | USE_CASE_CRITICAL_CUSTOM | Custom flow forced into face validation. |
| Sensitive (deprecated) | USE_CASE_SENSITIVE_ACC_MANAGEMENT | Deprecated. Still accepted; use USE_CASE_CRITICAL_ACC_MANAGEMENT. |
| Sensitive (deprecated) | USE_CASE_SENSITIVE_FIN_TRANSACTIONS | Deprecated. Still accepted; use USE_CASE_CRITICAL_FIN_TRANSACTIONS. |
| Sensitive (deprecated) | USE_CASE_SENSITIVE_FIN_SERVICES | Deprecated. Still accepted; use USE_CASE_CRITICAL_FIN_SERVICES. |
| Sensitive (deprecated) | USE_CASE_SENSITIVE_CUSTOM | Deprecated. Still accepted; use USE_CASE_CRITICAL_CUSTOM. |
Availability
| Surface | Supported |
|---|---|
| SDK (Android, iOS, Flutter) | ✅ |
| Web (iFrame, Redirect) | ✅ |
| API (headless, no SDK) | - |
Valid combinations
Smart Revalidation appears in the idsmart flow.
For the full matrix, see Available flows.