How it works
A partner takes the vendor's platform and replaces the logo, colour palette, email sender domain and mobile app name with their own. The end employer and their staff see only the partner brand. The vendor still hosts the code, processes the data and ships the updates. That split, brand on top, vendor underneath, is what separates white-label from a co-branded landing page.
Commercials usually follow one of two contract shapes. Under a reseller agreement the partner buys at a wholesale rate, sells to the end employer at their own price and books the revenue. Under an agency or introducer agreement the partner takes a commission and the vendor invoices the employer directly. The difference matters for VAT, accounting and reporting any taxable benefits the platform delivers, which the employer must still declare to HMRC under the Expenses and benefits: A to Z employer guidance.
If the platform resells anything regulated by the Financial Conduct Authority, such as certain prepaid vouchers, insurance or credit products, the partner sits inside a distribution chain. The FCA's Consumer Duty information for firms makes clear that distributors must understand the target market and how the product works, not just slap a brand on it.
What it isn't (common confusions)
White-label is not a logo swap on an iframe. An iframe still loads the vendor's domain in the browser address bar, leaks the vendor brand in cookies and email senders, and breaks single sign-on. A true white-label deployment runs on the partner's domain, sends from the partner's email and ships in an app store listing owned by the partner.
It is also not the same as a co-branded partner page, where both logos appear and the vendor's name is still visible to the end user. Co-branding suits introducer deals; white-label suits resale where the partner wants the employer relationship to be theirs alone.
A partner is not exempt from data protection duties just because the brand is theirs. Where the partner and the vendor jointly decide what data to collect and why, UK GDPR Article 26 treats them as joint controllers and requires a written arrangement setting out who handles subject-access requests, breach notification and the privacy notice. CIPD's reward and benefits factsheet underlines that benefits sit inside a wider reward strategy, which means the employer keeps the controller role for staff data even when a reseller delivers the tooling.
How WagePerks does this
WagePerks ships white-label as standard at no extra fee. The full eleven-module platform runs at £4.50 per employee per month all-in on a rolling monthly contract, with the partner's logo, colours, domain and app name on every screen. See payroll company partner economics for the wholesale and margin model.
Related on WagePerks
- White-label feature page — what gets rebranded
- Payroll company partner economics — wholesale and margin
- Payroll company recurring revenue guide — the unit economics
- Pricing — what's included at £4.50 per employee per month
Sources
- Expenses and benefits: A to Z — HMRC / GOV.UK — employer obligation to report benefits to HMRC, including benefits delivered via third parties
- Consumer Duty information for firms — FCA — distributor duties inside a distribution chain when reselling regulated products
- UK GDPR Article 26 — legislation.gov.uk — joint controller test and the requirement for a written arrangement
- Employee benefits factsheet — CIPD — benefits sit inside the employer's wider reward strategy, which anchors the controller role with the employer
Sources verified 2026-06-10. We re-verify quarterly.