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.
- Facial Biometric — reserved for high-risk transactions; runs liveness detection and facematch against the user's registered biometric.
Possible responses
| Response | Meaning |
|---|---|
YES | This is the expected user. |
NO | This is not 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 | Flows returning to the client's platform, such as passwordless login, check-in, identity revalidation, and keeping the online session alive. |
ACC_MANAGEMENT | Account profile change flows, such as password change, device swap, address update, etc. |
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. |
CRITICAL | Facial Biometric only. |
useCase enum values
| Category | Enum value | Description |
|---|---|---|
| Experience | USE_CASE_LOGIN | Optimizes UX for return flows to the client's platform, such as passwordless login and check-in. |
| Experience | USE_CASE_IDENTITY_REVALIDATION | Variant of USE_CASE_LOGIN for periodic identity revalidation with an extended validity window (7-day session / 30-minute step-up), used for the iGaming use case in Brazil. |
| Experience | USE_CASE_ACC_MANAGEMENT | Optimizes UX for account profile change flows, such as password change, new device, address update, etc. |
| Experience | USE_CASE_FIN_TRANSACTIONS | Optimizes UX for financial transaction flows such as PIX/TED (Brazil), Venmo/Zelle (US), cash withdrawal, etc. |
| Experience | USE_CASE_FIN_SERVICES | Optimizes UX for financial service applications, such as contracts and loans. |
| Experience | USE_CASE_CUSTOM | Optimizes UX for flows other than those mentioned above. |
| Critical | USE_CASE_CRITICAL_ACC_MANAGEMENT | Facial biometrics for account profile changes in more critical cases from the customer's perspective, such as account recovery or frequent profile changes. |
| Critical | USE_CASE_CRITICAL_FIN_TRANSACTIONS | Facial biometrics for critical monetary transactions, such as high-value ones. |
| Critical | USE_CASE_CRITICAL_FIN_SERVICES | Facial biometrics for critical financial service applications, such as sensitive contracts and loans. |
| Critical | USE_CASE_CRITICAL_CUSTOM | Facial biometrics for critical flows in use cases not mentioned above. |
Availability
| Integration components required |
|---|
| Web or SDK |
Valid combinations
Smart Revalidation appears in the idsmart flow.
For the full matrix, see Available flows.