> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/sdks/branding.md). # Branding ## Branding Overview ComplyCube Branding helps you align identity verification, KYC, and AML onboarding experiences with your product across the **Web SDK**, **Hosted Solution**, and **mobile SDKs**. From a single workspace, you can customize colors, logos, text, and other visual elements to deliver a consistent brand experience throughout the customer verification journey. This helps you deliver a consistent branded experience across every customer touchpoint. The Branding Canvas includes a **live preview**, allowing you to review and validate branding updates before publishing them to production.

Manage colors, text, logos, and preview changes from one place.

{% hint style="info" %} Branding settings are available in the [ComplyCube Portal](https://portal.complycube.com/settings/branding), if supported by your plan. {% endhint %} {% hint style="info" %} Branding settings are global by default. Supported SDKs can override selected settings during SDK initialization when you need a different experience for a specific integration. {% endhint %} ## Customizations Branding controls are configurable, allowing you to customize both visual styling and branded content. ### Color Customize color tokens across the verification experience, such as **surface**, **primary**, **secondary**, **tertiary**, **error**, **info**, and **success**. Each token can include values for the main background color and the color used on top of that background.
This lets you control the look and readability of interface elements such as: * Screen and panel surfaces. * Primary and secondary actions. * Form elements, status messages, and feedback states. ### Logo Upload supported logo assets to keep each flow aligned with your brand across different surfaces and display modes. This can include: * A main logo shown at the start of the verification flow. * Footer logos for light mode and dark mode. * A text logo fallback when image assets are not provided or cannot be loaded.
### Shape Adjust layout spacing and corner styling to better match your product design system. This can include controls such as: * Padding values across size categories, such as small, medium, large, and extra large. * Corner rounding for interface elements. * Advanced shape settings for more granular control where supported.
### Text Adjust typography styles used across the verification flow to better match your product voice and design system. This can include text styles such as: * Title and subtitle styles. * Larger body text used for prominent content and input labels. * Additional text categories exposed by the Branding workspace. Supported text settings can include properties such as font weight, size, and line height.
### Other Some branding settings extend beyond visual styling and allow you to customize platform behavior and theme configuration. Certain settings only apply to supported mobile SDKs or other mobile surfaces. These can include: * Behavior controls, such as haptics and animations on supported mobile platforms. * Theme settings, including light and dark presentation modes. * Business information, such as support email details.
## Preview changes The branding canvas gives you a live preview as you edit. You can validate changes before they reach production. You can also test existing workflows and verifications in sandbox to review the applied theme in a more complete flow. ## Publishing changes Changes made in the Branding canvas are not applied until saved. Once saved, updated branding is automatically applied across supported ComplyCube platforms, including hosted experiences and SDKs. ## Supported platforms Branding is supported across ComplyCube’s primary verification channels, including: * [Hosted Solution](/documentation/sdks/web-integrations/hosted-solution-quick-guide.md) * [Web SDK](/documentation/sdks/web-integrations/web-sdk-quick-guide.md) * [iOS SDK](/documentation/sdks/mobile-integrations/ios-sdk.md) * [Android SDK](/documentation/sdks/mobile-integrations/android-sdk.md) * [React Native SDK](/documentation/sdks/mobile-integrations/react-native-sdk.md) * [Flutter SDK](/documentation/sdks/mobile-integrations/flutter-sdk.md) * [Zapier](/documentation/sdks/third-party-integrations/zapier.md) * [Salesforce](/documentation/sdks/third-party-integrations/salesforce.md) ## White-label support ComplyCube supports a fully white-labeled solution for businesses that require a more deeply branded experience. This can include the removal of ComplyCube branding. Availability depends on your plan. ## Best practices * Keep button and text contrast high. * Preview every change before saving. * Use high-resolution logos that remain clear on both light and dark backgrounds. * Keep branding consistent with the rest of your product to reduce user confusion. * Avoid overly aggressive color combinations that may distract from key verification actions. * Review branding updates across multiple devices and screen sizes before deployment. ## Frequently asked questions
Are branding settings global by default? Yes. Branding settings apply globally across supported ComplyCube integrations by default. Supported SDKs can override selected settings during SDK initialization when needed.
Which ComplyCube integrations support branding? Branding supports the Hosted Solution, Web SDK, and supported mobile SDKs. Available controls can vary by platform.
Can I preview branding changes before publishing? Yes. The branding canvas provides a live preview while you edit. You can also test workflows and verifications in sandbox to review the applied theme in context.
When do branding changes go live? Branding changes do not go live until you save them. After saving, updates apply across supported platforms.
Is white-label branding available? Yes. ComplyCube supports fully white-labeled KYC and identity verification experiences on supported plans.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.complycube.com/documentation/sdks/branding.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.