Skip to main content
White-label the verification flow to match your brand identity, creating a seamless experience for your users. The workflow Academy lesson reaches white-labelling at 13:43, applying your branding to a live flow.

​
Customization

In the Style Editor you can customize everything in the verification UI:
White label style editor in the Business Console

​
Activate custom style in your workflow

After configuring your custom style, you must enable it per workflow for it to apply:
  1. Go to Workflows in the sidebar
  2. Open the workflow you want to brand
  3. Click Settings (or the gear icon)
  4. Under Options, find Include custom style
  5. Enable the toggle
Custom styles only apply to workflows where Include custom style is enabled. If you don’t enable it, the workflow will use the default Didit branding.

​
Custom text

Beyond colors, logos, and layout, the Texts tab lets you override the wording of specific verification-flow screens and change how the completion screen behaves, without forking translations for every locale. Open Console → White Label → Texts to configure:
  • Text overrides — replace the wording of a fixed set of strings across the welcome screen, document selection, document capture, selfie intro, questionnaire navigation buttons, the completion screen, and common buttons like Continue and Retry. An override applies for one locale at a time, and you can set a different value per locale.
  • Completion screen mode — choose Decision (default) to show the real outcome on the final screen, or Submitted for review to always show a neutral “we received your data and are reviewing it” message, even when Didit already approved the session. Use this if your own product communicates the final decision to users later.
Text overrides and the completion screen mode apply everywhere the verification flow renders: the hosted web flow, the iOS SDK, and the Android SDK.

​
Dynamic placeholders

Override text can include these placeholders, resolved per user at render time: {stepIndex} and {stepTotal} are computed from the actual workflow the user is running, so the same stored string correctly renders “step 1 of 3” for a three-step workflow and “step 1 of 2” for a two-step workflow.
Each overridden string has a 500-character limit. The Texts tab supports every locale your application can translate into, which is a longer list than the language selector in the Style Editor. Use Auto-translate to draft overrides for other locales from a value you’ve written by hand, then review before saving.
Custom text and the completion screen mode are configured entirely from the Console and only apply where Include custom style is enabled for the workflow, same as the rest of white-label.

​
Setup

1

Open the Style Editor

Navigate to Console → White Label → Style Editor.
2

Configure visual elements

  • Select your brand colors using the color picker
  • Upload logos in both square and rectangular formats
  • Adjust typography and border radius settings
3

Set up custom domain (optional)

Serve the flow from your own subdomain instead of verify.didit.me. Follow Custom domain for the DNS records and verification steps.
4

Override text (optional)

Open the Texts tab to change the wording of specific screens per locale, or switch the completion screen to Submitted for review. See Custom text.
5

Enable in your workflow

For each workflow that should use your branding: Workflow → Settings → Options → Include custom style → enable.
6

Preview and test

Use the live preview to see changes in real-time. Test the full verification flow before going live.

​
Compliance responsibilities in white-label flows

White-labeling changes the branding of the verification flow. It does not remove your obligations as the controller of that user journey. Before you launch a white-label flow, make sure you:
  1. Tell the end user that your company is requesting the verification and that Didit powers the verification workflow.
  2. Link to your own privacy notice and any controller-side legal terms that apply to the journey.
  3. Link to Didit’s Verification Privacy Notice and End User Terms for Identity Verification.
  4. Collect explicit affirmative consent before document capture, selfie capture, liveness, or biometric processing whenever the applicable law or your legal position requires it.
  5. Keep any proof of notice or consent that your legal team requires in your own systems.
Using a custom domain or removing visible Didit branding does not eliminate Didit’s role as the verification provider. If you use a custom UI or an API-driven flow, you must surface the required disclosures in your own interface.