Match the hosted verification screens to your brand with colors, logo, fonts and custom text - and remember the toggle that has to be enabled per workflow.

Short answer

Design the style in Identity verification → Customization, then enable Include custom style on each workflow you want it applied to. That second step is the one people miss - without it the workflow still shows default Didit branding. Custom branding adds $0.20 per completed verification.

You can replace Didit's default look on the hosted verification screens with your own colors, logo, fonts, and text. This is done on the Customization page, and it's a two-step process: design your style, then turn it on for the workflow you want it to apply to.

#What you can customize

  • Colors - buttons, text, panels, and backgrounds; every color element
  • Typography - fonts that match your brand
  • Logos - the logo shown in the flow, and the favicon in the browser tab
  • Layout - border radius for panels and buttons
  • Welcome screen - show it or skip it, on the General tab
  • Text - override the wording on specific screens, and change how the completion screen behaves
  • Domain - host the flow on your own subdomain instead of verify.didit.me, covered in white label and custom domain
The Customization page in the Didit console with the Branding tab and a live preview of the verification flow
Customization previews changes against the real flow.

#Setting it up

  1. Open Customization

    In the Business Console, go to Identity verification → Customization. It has five tabs: General, Branding, Texts, Channels and Domain.

  2. Set your colors, logo, and fonts

    On Branding, upload your logo and favicon, set your colors (the page checks each one's contrast against the background) and pick your font. The preview next to the form shows the flow as you change it, on a phone or a desktop, screen by screen (on a narrow screen, press Show preview).

  3. Override text if you need to (optional)

    The Texts tab replaces the wording of specific verification-flow strings - welcome screen, document selection, capture, selfie intro, questionnaire navigation - one language at a time. Fields you leave empty keep the Didit default, and Translate to all fills the other languages from the one you wrote.

  4. Turn it on for the workflow

    Press Save changes (the header reads All changes live once everything is saved). Then, the step people miss: open the workflow you want branded, open Workflow settings → Options and enable Include custom style (the Customization switch at the top of the editor does the same), then save or publish the workflow. Without this, that workflow still shows default Didit branding even if you've designed a custom style.

Note

Custom style is enabled per workflow, not account-wide. If you have several workflows, check this toggle on each one you want branded. This is the single most common cause of "I set up branding and the flow still looks like Didit."

#What can't be changed

  • The "Secured by" line. The small "Secured by" text at the bottom of the flow is the one visible trace of the provider that white label does not remove today. If it matters for your case, tell support so the request is counted.
  • One custom style per application. Each application has a single style, shared by Sandbox and Live, so there is no separate light and dark palette that follows the user's system setting. Pick a palette that reads well in both, or keep the branding to logo and accent colours.

#Access requirements

Changing customization needs write access to Customization. A teammate with read-only access sees the section disabled rather than getting an error - so if the editor looks inert, check the role before reporting a bug. See inviting team members and setting roles.

#It costs $0.20 per verification

White label is a billable feature at $0.20 per completed verification on KYC, KYB and proof of address workflows, and it is paid from your plan credit or balance on top of the other checks. Biometric authentication, age verification, questionnaire, email and phone workflows include it at no charge. Two consequences worth knowing before you turn it on:

  • A workflow that was free becomes a paid workflow the moment custom style is enabled, which is a very common cause of an unexpected "not enough credits" error. See fixing a "not enough credits" error.
  • The $0.20 is additive, on top of the per-module prices. A white-labelled flow running ID verification is $0.20 + $0.15, not $0.20 total.

#What branding doesn't change

White-labelling changes how the flow looks, not who's responsible for it. You're still expected to:

  • Tell the person that your company is requesting the verification, and that a provider powers it behind the scenes.
  • Link your own privacy notice alongside Didit's.
  • Collect the consent your legal team requires before document, selfie, or biometric capture.

A custom domain or a fully custom UI doesn't remove these obligations - it means the disclosures need to live in your own interface instead of Didit's default screens. See how Didit protects your users' data.

#Next steps

Still stuck? Talk to a human.

Include your organization ID and the session ID you are asking about.

Contact support