Hosted Flows

Learn when to use Socure-managed UIs for data collection and verification instead of building custom front-end integrations.

A Hosted Flow (also called Socure Hosted UX) is a preconfigured RiskOS™ workflow with a Socure-managed end-user interface. Hosted Flows use the same evaluation runtime, enrichment pipeline, and decision 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, rules, and statuses 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

sequenceDiagram
    participant User as End User
    participant App as Your Application
    participant RiskOS as RiskOS™
    participant HF as Hosted Flow UI

    App->>RiskOS: POST /api/evaluation (workflow = hosted flow)
    RiskOS->>RiskOS: Run workflow until user-interaction step
    RiskOS-->>App: evaluation_paused (session URL)
    App->>User: Redirect to Hosted Flow URL
    User->>HF: Complete data collection / verification
    HF->>RiskOS: Submit collected data
    RiskOS->>RiskOS: Resume workflow → enrichments → rules → decision
    RiskOS-->>App: Webhook: evaluation_completed (decision + data)

Your application triggers an evaluation specifying a Hosted Flow workflow.
The workflow reaches a user-interaction step and pauses.
RiskOS™ returns an evaluation_paused response with a session URL.
You redirect the end user to the Hosted Flow URL.
The user completes the required interactions (consent, PII entry, OTP, document capture).
The Hosted Flow submits the data to RiskOS™.
The workflow resumes and processes the remaining steps using the same enrichment and decision pipeline as any custom workflow.
The final decision is delivered via webhook.

Because Hosted Flows are asynchronous workflows, see Synchronous vs Asynchronous 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 (Draft → Published → Live).

Related concepts

Workflows — Hosted Flows are a specialized workflow delivery model
Evaluations — Triggering a Hosted Flow is triggering an evaluation
Decisions — Hosted Flows produce the same decision values as custom workflows
Statuses & Lifecycle — Hosted Flow evaluations follow the same lifecycle states
Synchronous vs Asynchronous Evaluations — Hosted Flows are always asynchronous
Step-up Verification — Hosted Flows as a step-up delivery mechanism
Signals & Attributes — Data collected by Hosted Flows becomes workflow attributes
Set up Hosted Flows — Tutorial: configure a Hosted Flow
Hosted Flows Scope — Supported use cases and limitations

Updated 5 days ago