Customize the flow

The hosted flow is white-labelled: it renders with your logo, colours, copy and theme so the applicant sees your brand, not ThirdFactor's. Most styling is a tenant/workflow-level property set in the console — it applies consistently across every channel you send an applicant through. Only a small set of knobs (locale, prefill) is set per session at create time.

What is set where

Branding & theme

The Design panel in the workflow builder controls the look of the hosted page. Workflow-level values override tenant defaults, so a designer sees exactly what they styled. The customization blob the flow consumes supports:

Put together, that's the shape the flow reads at render time — an operator never edits this JSON directly (the Design panel writes it), but it's useful to see the whole object when you're debugging why something isn't rendering as expected:

{
  "primary_color": "#0F62FE",
  "logo_url": "https://cdn.acme.example.com/logo.svg",
  "button_radius": "md",
  "theme": "dark",
  "language": "en",
  "welcome_title": "Verify your identity",
  "welcome_message": "This takes about 3 minutes. Have your ID ready.",
  "button_text": "Start verification",
  "allow_upload": true,
  "allow_desktop": true
}

Dark mode

Set theme to dark (or light) in the Design panel to force a colour scheme. The hosted flow resolves the theme server-side from the session token before the first frame, so a dark flow paints dark immediately — there is no light flash before hydration on the loading and gate screens.

Locale

locale on POST /v3/session/ sets the UI language for that specific session (default en):

Request

{
  "workflow_id": "9c2f1c4e-9a2b-4f2f-8f0f-0f1f3f4f5f6f",
  "locale": "ne"
}

Response — locale itself isn't echoed back on the session object, but it takes effect immediately on the hosted page:

{
  "id": "6f0e2b7a-…",
  "session_kind": "user",
  "status": "not_started",
  "url": "https://acme.example.com/verify/<session_token>",
  "vendor_data": null,
  "decision": "in_progress",
  "expires_at": "2026-07-13T08:00:00Z",
  "created_at": "2026-07-12T08:00:00Z"
}

The flow ships English (en) and Nepali (ne) copy. Per-locale text can be overridden tenant-wide (see below), so locale selects which override set the applicant sees.

Copy overrides (translations)

Under Settings → Translations an operator can override any applicant-facing string per locale — for example the intro title, step instructions, or button labels. Overrides are keyed by the flow's i18n dictionary and validated against a curated catalog, so only real, applicant-safe strings can be set. They are merged into the flow at render time and honour the session locale.

{
  "en": { "kyc.intro.title": "Verify your identity with Acme Bank" },
  "ne": { "kyc.intro.title": "एक्मे बैंकसँग आफ्नो पहिचान प्रमाणित गर्नुहोस्" }
}

Terms & Conditions

Under Settings → Terms you can attach versioned Terms & Conditions to the flow's start screen, optionally requiring explicit acceptance before the applicant can proceed. T&C carry a version and per-locale title / body; editing the content bumps the version and pushes the superseded copy onto its history, and an acceptance record is captured against the session.

Prefill

prefill on POST /v3/session/ pre-populates identity fields so the applicant types less. Only a fixed set of keys is read (unknown keys are ignored):

{
  "prefill": {
    "full_name": "Aarav Sharma",
    "first_name": "Aarav",
    "last_name": "Sharma",
    "display_name": "Aarav",
    "date_of_birth": "1990-04-12",
    "email": "[email protected]",
    "phone": "9841000000",
    "nationality": "NP",
    "address_line1": "House 12, Baneshwor",
    "address_line2": "Ward 10",
    "city": "Kathmandu",
    "state": "Bagmati",
    "country": "NP",
    "zip_code": "44600"
  }
}

See Create a session for the full field reference.

Hosted flow vs. SDK customization

Both delivery paths render the same Design-panel branding — the difference is what else you can control from the host application:

Troubleshooting

FAQ

Related