Developer Workflows for Composable Liveness Detection Fallbacks
Designing robust liveness detection workflows requires strategic fallbacks to maintain user experience and security. This involves understanding different liveness methods, configurable warning thresholds, and dynamic.

Strategic Liveness FallbacksImplement a layered approach to liveness detection, starting with the most secure methods and gracefully falling back to less stringent options based on user context, device capabilities, and risk profiles to balance security and user experience.
Understanding Liveness MethodsDifferentiate between 3D Action & Flash (highest security), 3D Flash (high security), and Passive Liveness (standard security) to select the appropriate method for various use cases and risk levels.
Configurable Warning and Decline ConditionsLeverage configurable thresholds for liveness scores, face quality, and potential spoofing attempts to automate decisions (approve, review, decline) and reduce manual intervention.
Didit's Modular OrchestrationUtilize Didit's AI-native, modular platform with its no-code Business Console and clean APIs to build flexible, composable liveness workflows with dynamic fallbacks, ensuring global scalability and free core KYC.
In the evolving landscape of digital identity verification, liveness detection stands as a critical barrier against spoofing and deepfake attacks. However, no single liveness method is a silver bullet for all scenarios. Developers face the challenge of designing workflows that are both highly secure and user-friendly, accommodating varying device capabilities, network conditions, and risk appetites. This often necessitates implementing intelligent fallbacks for liveness detection.
The Importance of Composable Liveness Detection
Liveness detection, a core component of fraud prevention, verifies that a real, live person is present during a biometric verification, not a photo, video, or 3D mask. Didit offers a range of Liveness Detection methods, each with distinct security levels and user experiences:
- 3D Action & Flash: This method provides the highest security by combining randomized actions (like blinking or nodding) with dynamic light pattern analysis to confirm a 3D structure and real-time interaction. It's ideal for high-risk applications like banking and healthcare.
- 3D Flash: Offering high security, this method projects light patterns to create a depth map of the face, distinguishing it from flat images. It's seamless and effective against photos and 2D spoofs, suitable for financial services and account access.
- Passive Liveness: This standard security method relies on single-frame deep learning analysis to detect artifacts and texture patterns indicative of liveness. It's fast and convenient for low-friction scenarios and consumer applications.
A composable approach means integrating these methods dynamically. Instead of a rigid, one-size-fits-all solution, developers can orchestrate a sequence of checks, allowing for graceful degradation or escalation based on initial results, user context, and predefined business rules. This flexibility is paramount for optimizing both security and conversion rates.
Designing Effective Fallback Workflows
Building a robust liveness detection workflow involves anticipating potential failures and having clear, automated paths for resolution. Here’s how developers can design effective fallback strategies:
1. Prioritize Security with Intelligent Escalation
Start with the most secure liveness method for high-risk transactions. If a user's device doesn't support 3D Action & Flash (e.g., no depth sensor, poor lighting for flash analysis), or if the initial attempt fails due to user error (e.g., didn't blink correctly), the system should intelligently fall back to the next most secure method, such as 3D Flash. If that also presents issues, a final fallback to Passive Liveness can be employed, perhaps triggering additional identity checks like ID Verification or Phone & Email Verification to compensate for the reduced liveness security.
Didit's modular architecture allows developers to define these orchestration rules within a no-code Business Console or via clean APIs. For instance, a workflow could be configured: Try 3D Action & Flash > if fail or unsupported, try 3D Flash > if fail, try Passive Liveness AND trigger a manual review or additional ID check.
2. Leverage Configurable Warning and Decline Conditions
Didit's Liveness Detection report provides comprehensive insights, including a liveness score, method used, and detailed warnings. Developers can configure how the system handles various issues:
- Low Liveness Score: Set review and decline thresholds. For example, a score below 70 might trigger an "In Review" status, while a score below 50 results in an automatic "Declined."
- Face Quality and Luminance: For Passive Liveness, thresholds can be set for low or high face quality/luminance, prompting a re-attempt or a switch to a more robust method.
- Automatic Declines: Conditions like
NO_FACE_DETECTED,LIVENESS_FACE_ATTACK(spoofing attempt), orFACE_IN_BLOCKLIST(matching a known fraudster via 1:1 Face Match & Face Search) will always result in an automatic decline, regardless of fallback settings.
By defining these rules, developers can automate decision-making, reducing the need for manual review and speeding up the verification process for legitimate users while maintaining strong fraud prevention.
3. Optimize User Experience with Clear Guidance
When a liveness check fails, providing clear, actionable feedback to the user is crucial. Instead of a generic "failed," the system should explain why it failed (e.g., "Please ensure your face is well-lit," "Try again and hold still," or "Perform the action clearly"). This helps users successfully complete the process on subsequent attempts, reducing frustration and churn. Fallbacks should also be communicated transparently, for example, "We're having trouble verifying your liveness with this method. Please try our alternative verification."
How Didit Helps
Didit is an AI-native, developer-first identity platform designed for building flexible and robust identity verification workflows. Our modular architecture allows businesses to compose verification steps, including advanced Liveness Detection, with dynamic fallbacks tailored to their specific needs. With Didit's no-code Business Console, developers can visually design complex orchestration flows, defining rules for when to escalate, de-escalate, or fall back to different liveness methods or other identity checks like ID Verification or Age Estimation.
Didit's advantages include:
- Free Core KYC: Get started with essential identity verification at no cost.
- Modular and Composable: Easily integrate various identity primitives, including Passive & Active Liveness, 1:1 Face Match, and NFC Verification, into custom workflows.
- AI-Native: Our advanced algorithms ensure high accuracy (99.9% for liveness) and robust fraud prevention against sophisticated attacks like deepfakes.
- No Setup Fees: Get started quickly and scale your operations without hidden costs.
- Detailed Reporting: Access comprehensive liveness reports with confidence scores, method details, and risk assessments to inform your fallback logic and manual review processes.
By leveraging Didit, developers can build resilient liveness detection systems that adapt to real-world conditions, minimize user friction, and maximize security, ensuring a seamless and secure onboarding experience.
Ready to Get Started?
Ready to see Didit in action? Get a free demo today.
Start verifying identities for free with Didit's free tier.