White Label in Forex Brokerage: Definition and Models

What white label forex brokerage means

In fintech, white label describes a product that one company builds and another company sells under its own brand. In forex brokerage, that product is usually the trading stack: a trading platform, a client portal, a back office and the connections that link them to liquidity and payments. The client sees the broker's name on the login screen, the client agreement and the statements.

The term has a wider meaning in other markets, which is outside this page. The same label can hide very different rights, so the contract matters more than the name.

For a broker, the practical questions are not whether a logo can be added. They are who holds the permission to serve clients, who controls the software, and what happens to client data and the brand if the arrangement ends. The white label brokerage answer covers the same ground in a broader question-and-answer format, including roles, licensing rights, brand, client data and exit.

Platform licence and regulatory licence are not the same

Two licences are often confused. A platform or software licence is a right to use trading software on the vendor's terms. A regulatory licence, or authorisation, is permission from a financial regulator to carry on regulated activities with clients. One comes from a software vendor and the other from a regulator. Holding one does not give you the other.

MetaQuotes describes itself as a software development company that does not provide investment or brokerage services. Its broker pages describe three licence types, Entry, Standard and Enterprise, that differ in real-account capacity and included system components. They also state that the broker deploys the software on its own hardware and that MetaQuotes does not offer SaaS or similar solutions that would permit even partial external management or third-party control of a broker’s operations (MetaQuotes, MetaTrader 5 for brokers). A platform licence therefore answers a software question. It does not answer the regulatory one.

In the UK, the FCA’s authorisation guidance says a firm must not start performing regulated activities while its application is under review, unless an exemption or temporary permission applies. It also says that carrying on regulated activities without authorisation is a criminal offence. A separate FCA page on appointed representatives says an appointed representative carries on regulated activity under the responsibility of an authorised firm, known as the principal. This page does not say whether that route is available for any activity. These are UK examples. For any other market, check the regulator where the clients are served.

White label, brokerage as a service and full licence compared

This page compares three models. They answer different questions, and vendor names do not always match the definitions below. The table compares them by who holds each right and duty.

• Who takes the client
  White label: The brand owner
  Brokerage as a service (BaaS): The brand owner, with the provider running more of the operation under contract
  Full licence: The company itself
• What the provider supplies
  White label: A branded platform and back-office systems
  Brokerage as a service (BaaS): Platform access plus modules such as CRM, payments, liquidity connections and reporting
  Full licence: The platform licence from the software vendor; the company sources hosting, CRM, payments and liquidity itself
• Who holds the software right
  White label: The provider or its licence holder, extended to the brand owner by contract
  Brokerage as a service (BaaS): The provider or a hosting partner, under a service contract
  Full licence: The company, under its own platform licence from the software vendor
• Who holds the regulatory permission
  White label: The brand owner, or an authorised firm it acts under where the regulator allows that route; the platform contract does not grant it
  Brokerage as a service (BaaS): Same as a white label: the service contract does not grant it
  Full licence: The company, under its own authorisation; the platform licence does not grant it
• Main contract check
  White label: Brand rights, data ownership, migration and exit terms
  Brokerage as a service (BaaS): Responsibility matrix, service scope and exit terms
  Full licence: Vendor contracts, internal capacity to run the stack, and the licence process

The table is a simplified view, and the lines overlap in practice. A white label deal can include BaaS modules, and a full licence buyer can still rent hosting. For the BaaS model in more detail, read the brokerage as a service guide.

The diagram below shows the same three models as a grid: who takes the client, who holds the software right and who holds the regulatory permission.

Where the white label model fits, and where it does not

A white label arrangement suits a broker that already has, or is applying for, the permission it needs in its target market, and that wants a brand, a client relationship and go-to-market control without writing trading software. It is a weaker fit where the buyer needs control of source code, data flows or hosting locations from the first day.

• Good fit: a company with a route to the regulatory permission for its target clients, which wants a branded stack run under a written scope.
• Good fit: a team that is content to let the provider operate the platform and back office, provided the responsibility split is written down.
• Weaker fit: a buyer that needs full control of the code, the data pipeline or the server location from the start.
• Weaker fit: a company with no clear route to the regulatory permission for the market it wants to serve.

Questions to ask before you sign a white label contract

Use these questions to test a white label proposal. Each answer should appear in the contract or in a schedule to it, not only in a sales deck.

1. Who holds the software licence, and does the licence name the broker, the provider or a hosting partner?
2. Which legal entity is the client-facing broker in each market, and which permission does that entity hold there?
3. Who owns the client data, the brand and the domain names on exit, and in what format is the data returned?
4. Which systems are in scope, and which are separate contracts, such as liquidity, payments and market data?
5. What notice, migration support and cut-over steps apply if the arrangement ends?

FxTrusts uses the same split in its own material. Our pricing page states that the Prop Firm CRM package price excludes the trading-platform licence and third-party API charges. Our pricing FAQ says that not every deployment needs a direct MetaQuotes licence, and that the licence holder and permitted use must be verified in writing.

Grey label and other terms you will meet

MetaQuotes lists three licence types for brokers, Entry, Standard and Enterprise, on its broker licence page. That page does not use the term grey label, so grey label is not one of those licence types. FxTrusts’ own pricing FAQ treats grey label as a market term, not a verified MetaQuotes licence category. A seller may still use grey label, white label, private label or reseller to describe a hosted or branded arrangement.

None of these labels tells you who holds the licence, who is the regulated entity, or who owns the brand. Read the contract for those facts. For the MetaTrader 5 side of the decision, an FxTrusts article covers licence holder and contractual rights. A platform-focused read is in our platform guide for brokers.

Where FxTrusts fits in a white label decision

FxTrusts supplies brokerage technology and implementation services. Our solution page for white label scope describes the items we define with a broker: the MT5 access model, CRM and back office, liquidity connections and a responsibility matrix. FxTrusts is a technology provider. It is not a licensed broker, bank or regulated financial institution, and it offers no retail trading accounts.

An FxTrusts technology contract does not give a broker regulatory permission, and FxTrusts does not hold the client relationship. The client relationship stays with the brand owner. Regulatory permission stays with the brand owner, or with an authorised firm it acts under where the regulator allows that. Where a platform licence or hosted access depends on a third party, the scope must say so. We do not treat a vendor statement as a substitute for the written licence holder and permitted use.