Ship-Mode Verification: Faster Onboarding with Didit

In today’s competitive landscape, a frictionless user onboarding experience is paramount. Every extra step, every delay, translates to lost users and revenue. Ship-mode verification is a technique to optimize onboarding flows by deferring non-essential identity checks to a later time, allowing users to quickly access your product or service. This approach, when implemented correctly, drastically reduces friction and increases conversion rates. Didit's composable flows and robust API make implementing ship-mode verification straightforward and effective.

Key Takeaway 1: Ship-mode verification prioritizes immediate user access by deferring less critical identity checks.

Key Takeaway 2: Didit’s modular architecture allows for a flexible and customizable ship-mode implementation.

Key Takeaway 3: Asynchronous processing with webhooks ensures deferred checks are completed without interrupting the user experience.

Key Takeaway 4: Data enrichment and risk scoring can be used to dynamically adjust the level of ship-mode verification.

What is Ship-Mode Verification?

Traditional KYC (Know Your Customer) and identity verification processes often involve a series of synchronous checks – ID document verification, liveness detection, AML screening, etc. – that the user must complete before gaining access. This can be slow and frustrating, leading to high drop-off rates. Ship-mode verification flips this approach. Instead of blocking access until all checks pass, you allow the user immediate access with only the most critical checks performed upfront. Non-critical checks are “shipped” to be completed in the background, asynchronously.

Imagine a ride-sharing app. Instead of requiring full KYC immediately, you might allow a user to request a ride after verifying their phone number and basic email address. More comprehensive checks (ID verification, background checks) can then run in the background, triggered by the ride request, without interrupting the user's immediate experience. This provides value to the user now while ensuring compliance and risk mitigation.

Building Ship-Mode Flows with Didit

Didit’s composable flow architecture is ideally suited for ship-mode verification. You can easily create workflows that separate critical and non-critical checks. Here’s how it works:

• Define Critical Checks: Identify the minimum checks required for initial access. This might include email verification, phone number verification, or passive liveness detection.
• Defer Non-Critical Checks: Move checks like full ID verification, AML screening, or database validation to a deferred stage.
• Asynchronous Processing: Use Didit’s API and webhooks to trigger these deferred checks in the background. Didit will notify you when these checks complete, allowing you to update the user's profile and risk score accordingly.
• Dynamic Adjustment: Implement logic to dynamically adjust the level of ship-mode verification based on risk factors (e.g., country, transaction amount, device fingerprint). Higher-risk users might require more upfront verification.

Example API Call (Triggering Deferred Verification):

POST /v1/workflows/shipmode
{
  "user_id": "user123",
  "workflow_id": "deferred_kyc",
  "context": {
    "transaction_amount": 100
  }
}

Benefits of Ship-Mode Verification

• Reduced Friction: Faster onboarding leads to a better user experience.
• Increased Conversion Rates: Less drop-off during onboarding translates to more customers.
• Improved Scalability: Asynchronous processing offloads work from the main user flow, improving scalability.
• Enhanced Risk Management: Deferred checks still provide comprehensive risk assessment, albeit at a later stage.
• Composable workflows: Using Didit's composable-flows allows you to quickly adjust to changing regulations

Didit customers have reported a 15-30% increase in onboarding completion rates by implementing ship-mode verification. Furthermore, the reduction in manual review workload frees up compliance teams to focus on higher-risk cases.

Data Enrichment and Risk Scoring

Ship-mode verification doesn't mean compromising on risk management. Didit's data enrichment capabilities allow you to gather additional information about the user during the deferred verification process. This data can then be used to update the user's risk score and trigger appropriate actions. For example, if a deferred AML check reveals a potential match, you can immediately restrict the user's access or initiate a manual review.

How Didit Helps

Didit provides a comprehensive platform for implementing ship-mode verification:

• Composable Flows: Easily create custom workflows with critical and deferred checks.
• Asynchronous API: Trigger deferred checks with a single API call.
• Webhooks: Receive real-time notifications when deferred checks complete.
• Data Enrichment: Access a wealth of data to enhance risk assessment.
• Fraud Signals: Identify and prevent fraudulent activity.
• Scalable Infrastructure: Handle high volumes of verification requests without performance issues.

Ready to Get Started?

Ready to reduce onboarding friction and boost conversion rates with ship-mode verification?

• Request a Demo to see Didit in action.
• Explore our Documentation for detailed API documentation and integration guides.
• View Pricing and start building with Didit today!

FAQ

Q: What types of checks are best suited for ship-mode verification?

Checks that are not time-sensitive and do not directly impact immediate access are ideal. Examples include full AML screening, database validation, and detailed KYC checks. Critical checks usually include email/phone verification and passive liveness.

Q: How do I handle users who fail deferred checks?

You can implement a variety of actions, such as restricting access to certain features, requiring a manual review, or suspending the account. Didit’s webhook system allows you to automate these actions based on the check result.

Q: Is ship-mode verification compliant with KYC/AML regulations?

Yes, when implemented correctly. Ship-mode verification doesn't bypass compliance; it simply defers certain checks. It's crucial to ensure that all required checks are eventually completed, and you maintain a robust audit trail.