> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Find your use case

> Choose the right OneSDK integration for your business — starting with the fastest, most cost-effective option.

## Overview

OneSDK offers multiple ways to integrate identity verification into your customer onboarding — from fully managed hosted flows to deeply customised embedded components.

**For the vast majority of businesses, Hosted OneSDK is the right choice.** It works across web, mobile (via WebView), and even offline channels — with minimal engineering effort, lower total cost of ownership, and the fastest time to market.

This page helps you evaluate each integration approach so you can make the right decision for your business.

## Why Start with Hosted OneSDK?

Before evaluating integration options, it's important to understand why Hosted OneSDK is the recommended starting point — not just from a technical perspective, but from a **business** one.

<CardGroup cols={2}>
  <Card title="Fastest Time to Market" icon="rocket">
    Go live in **days, not months**. Hosted flows require minimal frontend work — just generate a link via the Portal or API and send it to your customers. No SDK installation, no component wiring, no release cycles.
  </Card>

  <Card title="Lower Total Cost of Ownership" icon="coins">
    FrankieOne manages hosting, uptime, security patches, vendor updates, and compliance changes. You avoid the ongoing engineering cost of maintaining a custom integration — freeing your team to focus on your core product.
  </Card>

  <Card title="Always Compliant & Up to Date" icon="shield-check">
    Hosted flows are automatically updated to meet the latest regulatory and vendor requirements. No need to redeploy your app when compliance rules change.
  </Card>

  <Card title="Works on Web & Mobile" icon="mobile">
    Hosted OneSDK runs seamlessly in browsers **and** inside native mobile apps via WebView (Android and iOS). One integration covers all your platforms — no separate mobile SDK needed.
  </Card>

  <Card title="Customisable to Your Brand" icon="palette">
    Hosted doesn't mean generic. Add your company logo, apply your brand theming (colours and fonts), toggle optional screens (welcome, consent, review), and customise copywriting on key screens — all without writing frontend code.
  </Card>
</CardGroup>

<Callout icon="thumbtack" color="#1A6CFF" iconType="regular">
  **The bottom line:** Hosted OneSDK gives you the best balance of speed, cost, and reliability. Embedded or custom integrations should only be considered after hosted SDK options have been exhausted.
</Callout>

## Choose Your Integration Approach

### 1. Hosted OneSDK via Portal — No Code Required

**Best for**: Teams who want to start verifying customers immediately with zero engineering work.

Send verification links directly to your users via the FrankieOne Portal — by email, SMS, or QR code. 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

**Business impact:** Live in **as little as 1 day** | **No engineering cost** | Fully managed by FrankieOne

### 2. Hosted OneSDK via API — Automated, Scalable

**Best for**: Businesses that want to automate onboarding at scale while keeping engineering effort low.

Through a single API call, generate verification links dynamically and deliver them via your own channels — redirect to a new tab, embed in an iframe, integrate into your CRM, or send via email/SMS.

**Ideal for:**

* Online onboarding journeys (web or mobile web)
* Platforms sending large volumes of verification links
* Teams with strong backend capabilities but limited frontend resources

**Business impact:** Live in **1–2 weeks** | **Minimal frontend cost** | Fully managed by FrankieOne

### 3. Hosted OneSDK in Mobile Apps — Via WebView

**Best for**: Mobile-first businesses that need identity verification inside their native app without building a custom UI.

Hosted OneSDK works inside Android WebView and iOS WKWebView, giving your mobile users the same fully managed verification experience — including IDV with document scanning and selfie capture. There is no need to build or maintain a native SDK integration.

**Ideal for:**

* Native mobile apps (iOS and Android) requiring in-app verification
* Teams that want to avoid the complexity and cost of a native SDK integration
* Businesses that need camera, location, and biometric capture on mobile

**Business impact:** Live in **2–4 weeks** | **No native SDK maintenance** | Same hosted reliability on mobile

#### Mobile Sample Apps

We've published complete working examples for five mobile frameworks. Each sample app loads a Hosted OneSDK URL inside a native WebView — no custom UI or SDK embedding required.

**Prerequisites**

* A **FrankieOne Customer ID** and **API Key**
* **Hosted OneSDK enabled** on your account — contact your Customer Success Manager if you haven't set this up yet

<CardGroup cols={3}>
  <Card title="Android" icon="android" href="https://github.com/frankieone/frontend-onesdk-public-sample-codes/tree/main/mobile-onesdk-sample-android" />

  <Card title="iOS" icon="apple" href="https://github.com/frankieone/frontend-onesdk-public-sample-codes/tree/main/mobile-onesdk-sample-ios" />

  <Card title="React Native" icon="react" href="https://github.com/frankieone/frontend-onesdk-public-sample-codes/tree/main/mobile-onesdk-sample-react-native" />

  <Card title="Flutter" icon="mobile" href="https://github.com/frankieone/frontend-onesdk-public-sample-codes/tree/main/mobile-onesdk-sample-flutter" />

  <Card title="Expo" icon="mobile" href="https://github.com/frankieone/frontend-onesdk-public-sample-codes/tree/main/mobile-onesdk-sample-expo" />
</CardGroup>

<Callout icon="star" color="#3DD892" iconType="regular">
  **Try it now on Android** — download the pre-built APK directly from [GitHub Releases](https://github.com/frankieone/frontend-onesdk-public-sample-codes/releases) to see Hosted OneSDK running inside a native WebView. APKs are available for Android (Kotlin), React Native, Flutter, and Expo.
</Callout>

### 4. Embedded OneSDK — Custom Integration (Enterprise Only)

<Callout icon="bell" color="#FFCA16" iconType="regular">
  This option is **not recommended for most customers**. It requires significant engineering investment and ongoing maintenance. Only consider this if hosted flows cannot meet a specific business or regulatory requirement.

  Unlike hosted flows, embedded integrations run client-side — meaning **your team is responsible for keeping the SDK up to date**, including security patches, vendor changes, and compliance updates. Falling behind on updates can introduce security vulnerabilities and break verification flows.
</Callout>

**Best for**: Enterprise teams with unique workflows, regulatory constraints, or highly branded in-app verification requirements that cannot be achieved with hosted flows.

This approach involves embedding the OneSDK JavaScript library directly into your product and building your own verification flow using SDK modules (e.g. OCR, biometrics, fraud detection).

**Consider only when:**

* Verification must be deeply embedded into a proprietary product experience
* You have highly complex UI/UX requirements that hosted templates cannot support
* Regulatory or contractual obligations require self-hosted verification flows
* You have dedicated frontend engineering resources for ongoing maintenance

**Business impact:** **2+ months** to launch | **High engineering & maintenance cost** | You own hosting, updates, and compliance

## Comparison Summary

|                         | Hosted via Portal                                                       | Hosted via API                                                          | Hosted via WebView (Mobile)                                             | Embedded SDK                |
| :---------------------- | :---------------------------------------------------------------------- | :---------------------------------------------------------------------- | :---------------------------------------------------------------------- | :-------------------------- |
| **Time to Launch**      | As little as 1 day                                                      | 1–2 weeks                                                               | 2–4 weeks                                                               | 2+ months                   |
| **Engineering Effort**  | None                                                                    | Low (backend only)                                                      | Low (WebView setup)                                                     | High (full frontend)        |
| **Ongoing Maintenance** | None — managed by FrankieOne                                            | Minimal                                                                 | Minimal                                                                 | High — you own it           |
| **Hosting**             | FrankieOne                                                              | FrankieOne                                                              | FrankieOne                                                              | Your infrastructure         |
| **Compliance Updates**  | Automatic                                                               | Automatic                                                               | Automatic                                                               | Manual redeployment         |
| **Platform Support**    | Web, mobile browser                                                     | Web, mobile browser, CRM                                                | Native iOS & Android apps                                               | Web (your app)              |
| **Customisation**       | Logo, theming, optional screens, copywriting (welcome, consent, result) | Logo, theming, optional screens, copywriting (welcome, consent, result) | Logo, theming, optional screens, copywriting (welcome, consent, result) | Full control                |
| **Who It's For**        | Operations, CX, pilot teams                                             | Backend-automated onboarding                                            | Mobile-first businesses                                                 | Bespoke enterprise projects |

## Making the Right Decision

When evaluating your options, consider these business factors:

**Total Cost of Ownership (TCO):** Embedded integrations require not just the initial build, but ongoing maintenance — SDK upgrades, vendor changes, compliance updates, bug fixes, and dedicated engineering time. Hosted flows eliminate this entirely.

**Time to Market (TTM):** Every week spent building a custom integration is a week your customers aren't being verified. Hosted flows let you go live in days and iterate from there.

**Risk:** Hosted flows are battle-tested and maintained by FrankieOne. A custom integration introduces risk around uptime, security, and compliance that your team must manage.

<Callout icon="lightbulb" color="#1A6CFF" iconType="regular">
  **Our recommendation:** Start with Hosted OneSDK — whether via Portal, API, or WebView. You can always evolve to a more customised integration later if your business needs change. Most customers find that hosted flows meet their requirements long-term.
</Callout>

## What Verification Requirements Do You Have?

Regardless of your integration approach, OneSDK supports these verification types through hosted flow templates:

| Verification Requirement                     | Description                                                                 | Hosted Flow Template                            |
| :------------------------------------------- | :-------------------------------------------------------------------------- | :---------------------------------------------- |
| **IDV (OCR Document Scan + Selfie Capture)** | Verify identity through document and biometric capture.                     | IDV Template                                    |
| **Manual Data Entry for eKYC Checks**        | Collect data manually (name, DOB, address) for DVS or credit bureau checks. | eKYC Template                                   |
| **Additional Document Uploading**            | Request supporting documents such as proof of address or employment.        | Doc Upload Template                             |
| **Mixture of Verification Types**            | Combine multiple checks (e.g. OCR + AML + eKYC).                            | Custom Hosted or Embedded SDK (Enterprise Only) |

## What's Next

* **[Hosted Flow Templates](/docs/hosted-common-use-cases)** — Explore pre-configured IDV, eKYC, and document upload templates.
* **[Quick Start Guide](/docs/quickstart-guide)** — Implement your first hosted flow using either the Portal or API.
* **[Native Integration Guide](/docs/native-integration)** — Set up Hosted OneSDK inside Android or iOS WebViews.
* **[Using Hosted OneSDK](/docs/using-hosted-onesdk)** — Detailed implementation guide for hosted flows.
* **[Modifying Templates](/docs/quickstart-guide/modifying-templates)** — Customise branding, colours, and messaging on hosted flows.