> ## 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.

# Use Pre-built Pages & Hosted Flows

<Panel>
  **Get Started**

  <br />

  You can start using Hosted Flows immediately - no SDK installation required.

  <Steps>
    <Step title="Get API Credentials">
      Request your API key and Customer ID via the [FrankieOne Support Portal](https://frankieone.atlassian.net/servicedesk/customer/portals).
    </Step>

    <Step title="Test Integration">
      Use our [test data](/docs/test-data) to verify your implementation.
    </Step>

    <Step title="Monitor Verifications">
      Track verification statuses and analytics in the Portal.
    </Step>

    <Step title="Go Live">
      Switch to production credentials and start verifying users.

      ```bash title="1. Generate Onboarding URL" theme={null}
      curl --request POST \
           --url https://api.kycaml.uat.frankiefinancial.io/idv/v2/idvalidate/onboarding-url \
           --header 'api_key: API-KEY' \
           --header 'X-Frankie-CustomerID: CUSTOMER-ID' \
           --header 'accept: application/json' \
           --header 'content-type: application/json' \
           --data-raw '{
              "customerRef": "YOUR_UNIQUE_STRING",
              "consent": true,
              "flowId": "idv"
          }'
      ```

      Or generate and send verification links manually from the FrankieOne Portal.
    </Step>
  </Steps>
</Panel>

## What are hosted flows

**Hosted Flows** are FrankieOne’s fully managed, ready-to-launch verification experiences.

They allow you to onboard customers through FrankieOne’s hosted infrastructure — without building or maintaining your own verification UI or vendor integrations.

Each Hosted Flow contains all necessary steps, from data capture to identity verification and result delivery, and can be tailored to your brand through light configuration.

They are the fastest, most compliant, and most reliable way to start using OneSDK.

### Key Benefits

* **Zero Frontend Code**: No need to build or maintain verification screens.

* **Managed Compliance**: FrankieOne ensures vendor updates, regulatory logic, and security.

* **Consistent UX**: Professionally designed flow that works across devices.

* **Scalable**: Easily expand to multiple regions and verification types as you grow.

## Features

<CardGroup cols={2}>
  <Card title="Real-time Verification" icon="bolt">
    Instant document verification and liveness detection
  </Card>

  <Card title="Anti-Fraud Protection" icon="shield-check">
    Built-in protection against deepfakes and screen captures
  </Card>

  <Card title="Biometric Matching" icon="fingerprint">
    Advanced facial recognition and matching
  </Card>

  <Card title="Streamlined UX" icon="user">
    Intuitive flow for both desktop and mobile users
  </Card>
</CardGroup>

## Why use hosted flows

**Hosted Flows** are recommended for most customers because they combine speed, flexibility, and compliance with minimal engineering effort.

### Use Hosted Flows when:

* You want to start verifying customers quickly without frontend development.

* You need a fully managed, compliant onboarding experience.

* Your verification process can use standard, proven flow templates (eKYC, IDV, OCR).

* You want a consistent experience across multiple vendors and markets.

## How does hosted flow work

Hosted Flows run on FrankieOne’s infrastructure and connect directly to your account’s verification configurations and vendors.

They handle all client-side logic, event tracking, and result submission.

### Flow Overview

<Steps>
  <Step title="Start">
    The user is invited to complete verification (via link, redirect, or iframe).
  </Step>

  <Step title="Verification">
    OneSDK manages document capture, biometrics, or manual entry steps within the hosted interface.
  </Step>

  <Step title="Vendor Orchestration">
    FrankieOne routes verification requests to the selected vendor(s) and collects results.
  </Step>

  <Step title="Results">
    Verification outcomes are available in your Portal or returned via API webhook.
  </Step>
</Steps>

### Architecture

<Frame caption="High-level architecture overview">
  <img src="https://mintcdn.com/frankieone-f5583b1b/KtN8STJxha-rSSbB/images/v2/onesdk/image-20240912-041806.png?fit=max&auto=format&n=KtN8STJxha-rSSbB&q=85&s=567f6ca5389ace0433e7667fecda9693" alt="Architecture Diagram" width="1056" height="540" data-path="images/v2/onesdk/image-20240912-041806.png" />
</Frame>

1. Backend requests onboarding URL
2. User receives verification link
3. OneSDK handles document/biometric capture
4. Incode processes IDV data
5. FrankieOne KYC analyzes results
6. Status updates in Portal

## What’s Next

Once you’ve decided to use Hosted Flows:

1. **Choose a template** — select from our standard eKYC, IDV, or OCR-only flows.

2. **Add it to your account** — via the Portal or through FrankieOne support.

3. **Customise branding and messaging** — update logo, colours, and copy.

4. **Generate verification links** — send via Portal or API.

5. **Monitor results** — view verification outcomes in the Portal or through API webhooks.