Developer's Guide to Dynamic Fallback Workflows for IDV APIs

Proactive Error HandlingImplement robust error handling and retry mechanisms within your IDV API integrations to prevent verification failures from impacting user experience.

Multi-layered VerificationDesign workflows that incorporate multiple verification methods, allowing for seamless transitions to alternative checks if a primary method fails or yields inconclusive results.

Optimized User ExperienceUtilize dynamic fallbacks to guide users through alternative verification paths, minimizing friction and ensuring successful onboarding or transaction completion.

Didit's Orchestrated WorkflowsLeverage Didit's modular and AI-native platform to build and manage complex, dynamic fallback workflows with a no-code visual builder or clean APIs, ensuring maximum flexibility and reliability.

The Importance of Dynamic Fallback Workflows in IDV

In the world of online identity verification, relying on a single API call to confirm a user's identity is a recipe for potential failure and a poor user experience. Factors like poor document image quality, network latency, API rate limits, or even temporary service outages can disrupt the verification process. This is where dynamic fallback workflows become indispensable. A well-designed fallback strategy ensures that if a primary verification method fails, the system can intelligently pivot to an alternative, keeping the user journey smooth and maintaining high verification success rates. This not only improves customer satisfaction but also directly impacts conversion rates and operational efficiency.

For developers, building resilient systems means anticipating failure and having a plan B, C, and even D. Static, rigid verification flows often lead to users abandoning the process when encountering an error. Dynamic fallbacks, on the other hand, provide flexibility, allowing businesses to adapt to real-time conditions and user input. This is particularly critical for applications involving sensitive processes like customer onboarding, age verification for regulated content, or high-value transactions where robust identity assurance is paramount.

Designing Effective Fallback Logic

Implementing dynamic fallback workflows requires careful planning and a deep understanding of your verification needs. The core idea is to define a sequence of verification steps and conditional logic that dictates the flow based on the outcome of each step. Here's how to approach it:

1. Identify Potential Failure Points

Before designing fallbacks, you need to know what can go wrong. Common failure points in IDV include:

• Document Scan Issues: Blurry images, glare, incorrect document type, or expired documents can lead to failures in ID Verification (OCR, MRZ, barcodes).
• Liveness Detection Failures: Users failing liveness checks due to poor lighting, deepfakes, or non-compliance with instructions.
• Face Match Mismatches: Discrepancies between the document photo and the live selfie.
• Data Mismatches: Information extracted from a document not matching database records or user-provided data.
• AML Screening Flags: A user appearing on a watchlist requiring further manual review.
• API Service Interruptions: Temporary unavailability or errors from an identity verification provider.

2. Define Conditional Logic and Alternative Paths

Once failure points are identified, map out alternative paths. For instance:

• If an initial ID Verification (OCR) fails due to poor image quality, prompt the user to retake the photo or switch to a different document type.
• If Passive & Active Liveness detection indicates a high fraud risk, trigger a manual review or request additional proofs like Proof of Address.
• If a 1:1 Face Match fails, perhaps offer an alternative like Phone & Email Verification combined with specific knowledge-based authentication questions.
• For age verification scenarios, if Age Estimation is inconclusive, prompt for a physical ID scan.
• If an AML Screening & Monitoring check returns a potential match, automatically route the user to a compliance officer for further investigation without interrupting the user's flow.

Didit's Orchestrated Workflows, accessible via its no-code Business Console, are designed precisely for this, allowing you to visually construct complex decision trees and conditional steps without writing a single line of code. This modular approach means you can mix and match identity checks and easily define thresholds for success or failure.

3. Prioritize User Experience

Fallbacks should not feel like punishment. The goal is to keep the user engaged and reduce friction. Provide clear, concise instructions when a fallback is triggered. For example, instead of a generic error, tell the user, "Your document photo was blurry. Please try again in a well-lit area." or "We couldn't confirm your identity with this method. Would you like to try verifying with a different document or contact support?" Minimizing the number of steps and ensuring a consistent UI/UX across all verification paths is crucial.

Technical Implementation Strategies

From a technical standpoint, implementing dynamic fallback workflows involves several key considerations:

1. API Orchestration and State Management

Your backend system needs to orchestrate calls to various IDV APIs and manage the state of the verification process. This includes tracking which steps have been completed, which have failed, and which fallback paths have been initiated. Didit's API-first approach and the use of 'sessions' simplify this. When you create a session with a specific workflow ID, Didit handles the entire user-facing experience, state management, and conditional steps. You only need to query the session status to know the outcome.

GET /v3/workflows/
    - uuid: a1b2c3d4-5678-90ab-cdef-111111111111
      workflow_label: Standard KYC
      workflow_type: kyc
      features:
        - OCR
        - LIVENESS
        - FACE_MATCH
    - uuid: b2c3d4e5-6789-01bc-defg-222222222222
      workflow_label: Full Verification + AML
      workflow_type: kyc
      features:
        - OCR
        - LIVENESS
        - FACE_MATCH
        - AML

This API example shows how different workflows, each with distinct features like OCR, Liveness, Face Match, and AML, can be defined and accessed. You can then dynamically select the appropriate workflow based on initial verification results or user demographics.

2. Robust API Client and Error Handling

Your API client should be built to handle various HTTP status codes and error responses gracefully. Implement retry mechanisms with exponential backoff for transient errors. Differentiate between transient errors (e.g., network issues) and permanent errors (e.g., invalid input) to avoid unnecessary retries. Log all API interactions and error responses thoroughly for debugging and auditing purposes.

3. Modular and Composable Identity Checks

Adopt a modular architecture where each identity check (ID Verification, Liveness, Face Match, AML Screening, Proof of Address, Age Estimation, Phone & Email Verification) is a distinct, plug-and-play component. This allows you to easily swap out or add new verification methods without re-architecting your entire system. Didit's platform is built on this principle, offering composable identity primitives via clean APIs, making it easy to create custom workflows.

How Didit Helps

Didit is engineered from the ground up to empower developers with the tools to build sophisticated and dynamic identity verification workflows. Our AI-native, developer-first platform provides an open, modular identity layer that simplifies the implementation of fallbacks and complex verification journeys.

• Orchestrated Workflows: Didit's no-code visual builder in the Business Console allows you to design multi-step identity verification flows, including conditional logic nodes for KYC, age checks, and AML screening. You define the logic once, and Didit handles the user-facing experience, state management, and conditional steps. This means you can easily configure primary and fallback methods, like starting with ID Verification (OCR) and Liveness, and if a threshold isn't met, automatically triggering a Proof of Address request or manual review.
• Comprehensive Product Suite: With Didit, you have access to a full spectrum of verification tools, including ID Verification (OCR, MRZ, barcodes), Passive & Active Liveness, 1:1 Face Match & Face Search, AML Screening & Monitoring, Proof of Address, Age Estimation (privacy-preserving), Phone & Email Verification, and NFC Verification (ePassport/eID). This extensive toolkit allows you to build virtually any fallback scenario imaginable.
• Developer-First Approach: Didit offers an instant sandbox, public documentation, and clean APIs, making integration seamless. You can list, create, update, and delete workflows programmatically, giving you full control over your verification logic.
• Free Core KYC: Didit offers Free Core KYC, allowing businesses to get started and build robust workflows without upfront costs. Our pay-per-successful-check model and no setup fees mean you only pay when verification is successful, aligning costs with value.
• AI-Native Automation: By leveraging AI, Didit automates much of the decision-making process within workflows, reducing the need for manual review and speeding up verification times, even when fallbacks are engaged.

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.