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 four-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 to calculate a real-time risk level and determine which authentication tier to deploy.
- Silent Authentication — runs an AI-driven adaptive engine that scores device metadata, behavioral signals and the user's transaction history in the background to approve returning users with zero friction.
- Passkey — FIDO2-compliant authentication for mid-risk transactions, leveraging the device's built-in biometrics without requiring a selfie capture.
- Facial Biometric — reserved for high-risk transactions; runs liveness detection and facematch against the user's registered biometric.
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. |
SENSITIVE | Passkey and Facial Biometric only. |
CRITICAL | Facial Biometric only. |
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. |
| Sensitive | USE_CASE_SENSITIVE_ACC_MANAGEMENT | Passkey/Face for core credential updates. |
| Sensitive | USE_CASE_SENSITIVE_FIN_TRANSACTIONS | Passkey/Face for elevated transfer values. |
| Sensitive | USE_CASE_SENSITIVE_FIN_SERVICES | Passkey/Face for credit or card locking. |
| Sensitive | USE_CASE_SENSITIVE_CUSTOM | Custom flow requiring a hardware check. |
| 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. |
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.