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

# Beyond Journeys

> The two flows journeys don't assemble yet, and the from-scratch path if you need to orchestrate verification yourself.

<Callout icon="road" color="#1A6CFF" iconType="regular">
  **Journey coverage is planned for these flows.** Split capture and standalone document upload are
  the two remaining gaps, and both are on the journey roadmap. If your integration needs one of
  them, tell your Customer Success Manager — customer demand is how we decide which lands first.
  Until then, the guides below are the supported way to build them.
</Callout>

## Do you need this?

You need the from-scratch path only if you must:

* own the mount and unmount cycle yourself
* interleave your own UI inside a capture flow
* run OCR and biometrics as separately-timed steps
* collect supporting documents outside a KYC flow

Everything else is a journey — start with the [journey quick start](/docs/embedded-flows/journey/quick-start).

## What's here

<CardGroup cols={2}>
  <Card title="Split Flow (OCR + Biometrics)" icon="code-branch" href="/docs/embedded-flows/split-flow">
    Separate OCR and Biometrics components wired together, for when the two captures must be timed independently.
  </Card>

  <Card title="Document Upload" icon="cloud-arrow-up" href="/docs/embedded-flows/doc-upload">
    File-based collection of supporting documents outside a KYC flow.
  </Card>
</CardGroup>

## Orchestrating it yourself

If your requirement isn't one of the two above, you're building the flow from scratch, not assembling one that already exists. That means:

* mounting each step's component yourself
* listening for each module's events
* deciding what follows what
* handling every retry
* interpreting the result yourself

There's no journey underneath absorbing any of this — you own the flow, its upgrades, and its compliance behaviour. Start from the module pages you'll actually mount — [OCR](/docs/sdk-reference/ocr-module), [Biometrics](/docs/sdk-reference/biometrics-module), [IDV](/docs/sdk-reference/idv-module), and [Form](/docs/sdk-reference/form-module) — to see what each step exposes, and build up from there.

Pass-through screen configuration follows the same shape a journey would hand it — see [Form Module Configuration](/docs/sdk-reference/form-module/configuration) for the field-level detail.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.