Find your use case
Overview
OneSDK supports a variety of onboarding experiences — from simple “send a verification link” workflows to deeply integrated, branded in-app journeys.
This section helps you determine how OneSDK fits into your customer onboarding flow based on your verification requirements, desired customer experience, and technical capabilities.
For most customers, Pre-Built Hosted Flows offer the fastest, most reliable, and fully compliant way to launch. Other approaches, such as embedded or custom SDK implementations, are reserved for enterprise partners with bespoke, non-standard requirements.
What Verification Requirements Do You Have?
What Is Your Customer Experience?
Choose the approach that best fits your customer journey and technical setup.
Use the FrankieOne Portal to Send Verification Links
Best for: Teams who want to start verifying customers immediately with no engineering work.
Send verification links directly to your users via the FrankieOne Portal — by email, SMS, or CRM integration. Users complete the verification through a secure, FrankieOne-hosted flow, and results appear instantly in your Portal.
Ideal for:
-
Manual or semi-automated onboarding teams
-
Low - to medium - volume verification
-
Businesses piloting or validating their onboarding process
Recommended approach: ✅ Pre-built Hosted Flow (via Portal)
Generate Verification Links via an API Call
Best for: Businesses that want to automate the onboarding experience while FrankieOne manages hosting, uptime, and compliance
Through a single API call, you can generate verification links dynamically — redirecting the user to a new tab or embedding them into your CRM, onboarding system, or customer communications.
The flow remains hosted by FrankieOne, ensuring reliability while giving you full backend automation.
Ideal for:
-
Online onboarding journeys (web or mobile web) or CRM workflows
-
Platforms that need to send large volumes of verification links or scaling rapidly
-
Teams with limited frontend resources but strong backend capabilities
Recommended approach: ✅ Pre-built Hosted Flow (via API)
Build a Custom Integration with OneSDK Components (Enterprise or Bespoke Only)
This option is NOT recommended for most customers, requires bespoke implementation.
Best for: Enterprise teams with unique workflows, regulatory constraints, or highly branded in-app verification requirements.
This option involves embedding the OneSDK JavaScript library directly into your product and constructing your own flow using SDK modules (e.g. OCR, biometrics, fraud detection).
Consider only for:
-
Scenarios where verification is a deeply embedded part of the product experience
-
Large-scale enterprise platforms with highly complex UI/UX requirements
-
Regulated financial institutions needing bespoke KYC/AML orchestration
-
When hosted flows cannot meet business or regulatory needs
Mobile or Native App Integrations
Best for: Mobile-first businesses that require a fully native experience.
Currently, OneSDK do not support native mobile integrations. Mobile implementation is via Hosted OneSDK wrapped on webviews.
Comparison Summary
Here is that text converted into a Markdown table for you.
Recommendations
✅ Start simple, scale later.
Most customers should start with Pre-built Hosted Flows (via Portal or API). They’re quick to deploy, fully compliant, and managed by FrankieOne.
⚙️ Embed only when necessary.
Choose Embedded SDK or Mobile integrations only if your business model demands a custom, deeply integrated UX.
📈 Evolve gradually.
You can always start with a pre-built flow, then move to custom or embedded setups as your onboarding process matures.
What’s Next
-
Use Pre-Built Hosted Flows → Learn how to configure and launch a hosted flow in minutes.
-
Quick Start Guide → Implement your first flow using either the Portal or API.
-
API Reference → Review key endpoints for link creation and result retrieval.
