A **Hosted Flow** (also called **Socure Hosted UX**) is a preconfigured RiskOS™ [workflow](https://help.socure.com/riskos/docs/understanding-riskos#workflows) with a Socure-managed end-user interface. Hosted Flows use the same [evaluation](https://help.socure.com/riskos/docs/understanding-riskos#evaluations) runtime, [enrichment](https://help.socure.com/riskos/docs/understanding-riskos#enrichments) pipeline, and [decision](https://help.socure.com/riskos/docs/understanding-riskos#decisions) model as custom workflows — the difference is in ownership, configuration, and delivery.

Hosted Flows are workflows. They are not a separate execution model.

## Relationship to workflows

Hosted Flows are built on the standard RiskOS™ workflow/evaluation architecture:

- A Hosted Flow **is** a workflow with preconfigured steps, enrichments, and decision logic.
- Triggering a Hosted Flow **is** triggering an evaluation via `POST /api/evaluation`.
- The evaluation runtime processes the Hosted Flow identically to a custom workflow — the same [signals](https://help.socure.com/riskos/docs/understanding-riskos#signals--attributes), [rules](https://help.socure.com/riskos/docs/understanding-riskos#rules--conditions), and [statuses](https://help.socure.com/riskos/docs/statuses-and-lifecycle) apply.

The distinction is operational, not architectural.

## Hosted Flows vs custom workflows

| Aspect | Hosted Flow | Custom Workflow |
| --- | --- | --- |
| **Configuration** | Preconfigured by Socure | Customer-authored in Workflow Editor |
| **End-user UI** | Socure-hosted (web-based) | Customer-built (API + SDK) |
| **Lifecycle management** | Managed by Socure | Customer-managed (Draft → Published → Live) |
| **Flow design** | Opinionated — optimized for common use cases | Fully customizable — any step sequence |
| **Extensibility** | Limited to template customization and branding | Full access to all step types and third-party enrichments |
| **Enrichments** | Preconfigured enrichment set | Customer selects enrichments |
| **Decision logic** | Preconfigured rules and thresholds | Customer defines all rules and conditions |
| **Evaluation runtime** | Same | Same |
| **Decision model** | Same (`ACCEPT`, `REJECT`, `REVIEW`) | Same |
| **Webhook events** | Same | Same |
| **Case Management** | Same | Same |

## How Hosted Flows work at runtime

```
Hosted Flow UIRiskOS™Your ApplicationEnd UserHosted Flow UIRiskOS™Your ApplicationEnd UserPOST /api/evaluation (workflow = hosted flow)Run workflow until user-interaction stepevaluation_paused (session URL)Redirect to Hosted Flow URLComplete data collection / verificationSubmit collected dataResume workflow → enrichments → rules → decisionWebhook: evaluation_completed (decision + data)
```

1. Your application triggers an [evaluation](https://help.socure.com/riskos/docs/understanding-riskos#evaluations) specifying a Hosted Flow workflow.
2. The workflow reaches a user-interaction step and [pauses](https://help.socure.com/riskos/docs/statuses-and-lifecycle).
3. RiskOS™ returns an `evaluation_paused` response with a session URL.
4. You redirect the end user to the Hosted Flow URL.
5. The user completes the required interactions (consent, PII entry, OTP, document capture).
6. The Hosted Flow submits the data to RiskOS™.
7. The workflow resumes and processes the remaining steps using the same enrichment and decision pipeline as any custom workflow.
8. The final [decision](https://help.socure.com/riskos/docs/understanding-riskos#decisions) is delivered via [webhook](https://help.socure.com/riskos/docs/webhooks).

Because Hosted Flows are asynchronous workflows, see [Synchronous vs Asynchronous Evaluations](https://help.socure.com/riskos/docs/sync-vs-async-evaluations) for the full execution model.

## What Hosted Flows can collect

| Interaction | Description |
| --- | --- |
| **Consent** | User consent page before data collection |
| **PII form** | Basic or advanced personally identifiable information |
| **OTP verification** | One-time passcode via SMS, voice, or email |
| **Document capture** | Government-issued ID capture via Predictive DocV |
| **Selfie** | Biometric selfie for liveness check |

## Customization

You configure the Hosted Flow UI in the RiskOS™ Dashboard using the **Hosted Flow Builder**:

- **Templates**: Pre-built starting points for common use cases (Consumer Onboarding, Advanced Prefill)
- **Page Builder**: Drag-and-drop UX components and page templates
- **Brand themes**: Customize colors, logo, and typography (with AI-assisted auto-theming)
- **Responsive design**: Adapts to desktop and mobile browsers
- **Localization**: Multi-language support

> **Limitation**: Hosted Flows are web-based (WebView). Native iOS and Android Hosted Flows aren't supported.

## Save vs Publish

| Action | Effect |
| --- | --- |
| **Save** | Stores UI changes in the Sandbox environment |
| **Publish** | Pushes UI changes to the Production environment |

This applies to the Hosted Flow UI configuration only. The underlying workflow follows the standard [workflow lifecycle](https://help.socure.com/riskos/docs/understanding-riskos#workflows) (Draft → Published → Live).

## Related concepts

- [Workflows](https://help.socure.com/riskos/docs/understanding-riskos#workflows) — Hosted Flows are a specialized workflow delivery model
- [Evaluations](https://help.socure.com/riskos/docs/understanding-riskos#evaluations) — Triggering a Hosted Flow is triggering an evaluation
- [Decisions](https://help.socure.com/riskos/docs/understanding-riskos#decisions) — Hosted Flows produce the same decision values as custom workflows
- [Statuses & Lifecycle](https://help.socure.com/riskos/docs/statuses-and-lifecycle) — Hosted Flow evaluations follow the same lifecycle states
- [Synchronous vs Asynchronous Evaluations](https://help.socure.com/riskos/docs/sync-vs-async-evaluations) — Hosted Flows are always asynchronous
- [Step-up Verification](https://help.socure.com/riskos/docs/step-up-verification) — Hosted Flows as a step-up delivery mechanism
- [Signals & Attributes](https://help.socure.com/riskos/docs/understanding-riskos#signals--attributes) — Data collected by Hosted Flows becomes workflow attributes
- [Set up Hosted Flows](https://help.socure.com/riskos/docs/hosted-flows-riskos-setup) — Tutorial: configure a Hosted Flow
- [Hosted Flows Scope](https://help.socure.com/riskos/docs/hosted-flows-usage-scope) — Supported use cases and limitations

Updated about 1 month ago