What white-labelling actually means
In fintech, white-labelling means deploying a platform under a client's brand, domain, and — critically — regulatory context. It's not just visual rebrand. A financial platform operating under a new brand may need to reference different regulatory permissions, display different legal entities, and comply with the client's specific licence conditions.
A thorough white-label process covers five layers: visual identity (colours, typography, logo, imagery), product copy (feature names, error messages, notification text), legal and compliance copy (T&Cs, privacy policy, regulatory disclosures), domain and infrastructure, and where applicable, the underlying BaaS provider configuration.
Step 1: Audit your design tokens
A well-architected fintech template uses design tokens — CSS variables or a centralised theme configuration — rather than hardcoded colour values. Before you can white-label, you need to know exactly which tokens exist, what they control, and whether every colour in the UI actually references a token.
Walk through the UI systematically: the marketing site, the auth screens, the user dashboard, the admin panel. Document every element that carries colour, and check that it traces back to a token. Any hardcoded hex value is a liability — it won't change when you swap the theme.
BAAS Kit Pro templates use Tailwind CSS v4 with CSS custom properties as the token layer. A complete white-label means updating `--color-primary`, `--color-accent`, and the gradient definitions in `globals.css` — the rest propagates automatically.
Step 2: Replace all brand assets
Brand assets in a fintech platform extend beyond the logo. Conduct a systematic search for: logo files (SVG preferred — check all sizes and variants including favicon, app icon, and OG image), brand name in all its forms as string literals in the codebase, email sender name and reply-to address in notification templates, and any hardcoded URLs pointing to the template's own domain.
Use your code editor's global search to find every occurrence of the original brand name. It will appear in metadata titles, email subject lines, legal copy, and console log statements. Each one needs to be replaced — or better, extracted to a central config file that the white-label process updates in one place.
Step 3: Legal and compliance copy
This step is the one most teams underestimate. A fintech platform that processes real money must display specific legal copy tied to the licence holder. The Terms and Conditions must identify the correct legal entity, jurisdiction, and regulatory permissions. The privacy policy must reference the correct data controller and ICO registration number (in the UK). Any reference to FCA authorisation, PSD2 compliance, or safeguarding must be accurate to the specific licence.
Do not simply find and replace the company name in the existing T&Cs. Have the new entity's legal counsel review and approve the legal copy. This is not optional — it is a regulatory requirement. A fintech platform displaying incorrect regulatory disclosures is a Material Breach of Conduct risk.
Beyond legal copy, check all error messages, onboarding instructions, and support references. Any text that says 'contact [OriginalBrand] support' or references the original entity's processes needs to be updated.
Step 4: Domain, email, and infrastructure
Point the platform to the client's domain and configure all the supporting infrastructure that financial platforms require. DNS records for the main domain and any subdomains (app.clientbrand.com, admin.clientbrand.com, api.clientbrand.com). SSL certificates — automated with Let's Encrypt or a managed certificate provider. SPF, DKIM, and DMARC records for transactional email to ensure deliverability and prevent spoofing. A transactional email provider configured with the client's sending domain. And environment variables updated to reflect the new domain across all services.
Step 5: Test the full user journey
Before handing over a white-labelled platform, run through every user-facing journey end to end: public site → sign up → KYC onboarding → dashboard access → transaction → admin view → notification email. Check every screen for residual references to the original brand. Review every email notification for sender name, subject line, and body copy. Confirm that regulatory disclosures appear on every required screen. And test on mobile — many fintech platforms are predominantly mobile-used, and brand consistency on small screens is easy to miss.
A simple checklist shared between the delivery team and the client sign-off party prevents the embarrassing post-launch discovery of a logo or company name that wasn't updated.