Your brand and your domain

Everything an applicant sees during a verification can carry your brand. You set it once on a workflow in the console, and it applies wherever that workflow runs: the web SDK, the mobile SDKs and hosted links.

What you can change

Area	What it controls	Where
Colours and theme	Brand colour, button text, background, surface, border, text and the backdrop behind the modal, for light and dark screens	Workflow Settings, Branding
Fonts and corners	Heading font, body font and corner radius	Workflow Settings, Branding
Logo and company name	The mark and name at the top of the screens	Workflow Settings, Branding
Browser tab icon	The icon shown on hosted verification links	Workflow Settings, Branding
Wording	Titles, descriptions, labels and buttons on each screen	Workflow Settings, Texts
Welcome and success screens	The copy on the first and last screens	Consent and Success steps
Footer logo	Your logo in place of the Toden “Protected by” footer	Workflow Settings, Branding

Changes are saved to the workflow’s draft. Applicants see them after you publish. See Workflows for drafts, publishing and versions.

Colours, themes and fonts

Open a workflow in the console at console.toden.co, choose Workflow Settings, then Branding.

Brand colour is used for buttons, progress and highlights. You can also set the colour of the text on buttons.
Light or dark mode sets how the screens open: light, dark, or following each person’s device setting. You can give the dark screens their own colours and their own logo.
Overlay is the backdrop behind the web modal. It accepts an opacity.
Fonts are picked from the list the SDKs support, one for headings and one for body text.
A live preview beside the settings shows the applicant screens as you edit.

The preview in the builder runs the real web SDK with uploads and submissions switched off. Nothing is captured, sent or charged while you use it.

If you mount an SDK without a workflow, the same options are available as the appearance prop. When a workflow is used, the workflow’s appearance wins over the prop. See the SDK overview.

Logo and company name

The Logo row has three choices: Organisation (the logo saved on your organisation), Upload (a logo for this workflow only) or None. The Company name is your organisation name or a custom name.

Your organisation logo is also used in the preview card when a hosted link is shared in a chat or email, with your organisation name and the workflow’s brand colour.

Import your brand

You do not have to enter colours by hand. Import your brand reads them for you from one of two sources.

Your website

Brand guide

Enter your website address. Toden reads the public page and suggests your logo, a logo for dark screens where the site has one, your brand colours for both themes, and your fonts where the site names them.

Some websites answer automated visits with a bot check. Toden does not try to get past it. In that case use a brand guide instead.

An import only suggests. You review the result and choose what to apply. Nothing changes on the workflow until you apply it and save.

Custom wording

The Texts tab lists the wording on each screen the workflow can show: titles, descriptions, checklists, field labels, liveness instructions, outcome messages and buttons. Change a text to replace it. Clear it to return to the default.

Only the texts you change are stored. Everything else shows the standard wording.
Error messages, system messages, loading lines and the legal notice always keep the standard wording.
The editor writes English. To show another language, see Supported languages.
The welcome and success screens also have their own copy fields on the Consent and Success steps. Where both are set, those fields are used.

Adding or rewording a custom text follows the same unlock as the custom footer logo below. Texts you have already saved stay in place. The copy fields on the Consent and Success steps are available to every organisation.

By default the verification screens carry a small Toden “Protected by” footer. Custom Trust Branding replaces it with your own logo, so no Toden mark is shown in the footer.

Try it

Open the footer option under Branding, upload or pick a logo, and see it in the real footer on light and dark screens. You can do this at any balance.

Unlock it

Saving a custom footer logo for the first time needs paid credit at or above a minimum. The default minimum is $750. It can differ for your organisation, and the console shows your figure and how much more you need. Promotional credit does not count towards it.

Publish

Publish the workflow. Once your organisation has gone live with a custom footer logo, later logo changes on any workflow do not need the minimum again.

Detail	How it works
Charge	A fee per production verification while a workflow shows your footer logo. The console shows your price before you switch it on.
Sandbox	Free. Sandbox verifications are never charged.
Dark screens	You can add a second logo for dark screens. If you do not, the main logo is used on both. It costs nothing extra.
Default for new workflows	Set under Configure, Workflows, Settings, so new workflows start with your footer choice.
Consent notice	With your own footer logo, the consent screen states that the verification is processed by Toden for your organisation. This disclosure cannot be removed.

See Billing for how credit and charges work.

Hosted link domain

Hosted verification links are served from the Toden console host, for example https://console.toden.co/verify/.... The page itself carries your colours, logo, wording and tab icon, and the link preview shows your organisation name and logo.

See Hosted quickstart for creating and sharing a link.

Custom domain

Serving hosted verification pages from your own domain (for example verify.yourcompany.com) is not a self-service setting yet. The Domain tab in Workflow Settings shows the current Toden-managed domain and marks custom domains as coming soon.

If you need your own domain, contact hello@toden.co and we will tell you what is possible for your account.

If the address bar matters to you today, embed the flow in your own site or app with an SDK. The applicant then never leaves your domain or your app.

What stays the same

The steps, checks and decisions are unchanged by branding. Appearance never affects a verification result.
The legal and consent wording that names Toden as the processor stays in place.
Identifiers that still contain “Myaza”, such as @myazahq/kyc-sdk-react and <MyazaKYC/>, are current and unrelated to what applicants see.