A white-label casino normally places a consumer brand inside another licensee's regulated operation, while a turnkey platform normally supplies an integrated technology stack to an operator. These are commercial labels, not universal licence categories. Verify the licensee, customer contract, player funds, data roles, payment contracts and exit rights separately.
This guide is for founders, investors, procurement teams and affiliates evaluating an online casino launch. It compares control boundaries rather than vendors. It is not legal advice, a cost estimate or a promise about launch timing; the answer changes with the market, product, corporate structure and contract.
What do white label and turnkey mean in online gambling?
There is no global regulatory definition that makes every white-label or turnkey arrangement identical. Providers also package the terms differently. Treat them as starting points for due diligence, not as evidence of legal status.
The BETTIMES explainer on white-label gambling covers the basic brand-and-operator structure. This comparison starts at the next decision: which party controls each regulated, commercial and technical function.
In a 2025 explanation of white-label domain status, the British regulator described a white-label domain as one operated by a licensed operator in partnership with another organisation. The licence holder offers the gambling facilities and remains responsible for activity on the branded site. The partner may control branding or marketing, but it cannot provide the regulated gambling facilities itself unless it holds the relevant licence.
Turnkey usually describes a pre-integrated operational stack: platform, player-account tools, game or sportsbook connections, payments, reporting and optional managed services. The customer may hold its own licence and player relationship, but “turnkey” does not prove that. A contract can move individual functions back to the supplier, a group entity or a subcontractor.
| Role | What it means | Where to verify |
|---|---|---|
| Customer-facing licence | Relies on another operator's licence and regulated operation | Customer obtains or uses its own market authorisation |
| Player contract | Commonly sits with the licensed operator | Commonly sits with the customer operator |
| Technology stack | Shared stack and operating controls supplied by the licensee or its vendors | Integrated stack supplied to the customer under a platform contract |
| Compliance decisions | Licence holder keeps ultimate regulatory accountability | Customer licensee keeps accountability; supplier supports defined controls |
| Payments and funds | Often contracted and controlled through the licence holder's setup | May be customer-controlled, supplier-supported or split by function |
| Data and reporting | Access can be limited by the shared operation and contract | Customer may receive broader access, but export and controller roles still need terms |
| Brand and domain | Brand partner may own commercial assets while the operator declares or uses the domain | Customer often controls brand assets and domain, subject to supplier dependencies |
| Exit | May require re-papering the whole regulated and payment setup | May permit platform migration, but only if data, integrations and transition rights are portable |
These are tendencies, not legal conclusions. Ask for the documents that establish each row.
The licence holder is not the same thing as the platform provider
An online casino can involve several permissions. The entity offering gambling to players may need a customer-facing operating or gaming-service licence. A separate company may supply gambling software, host games, aggregate content or manage a critical control system under a supplier permission.
Great Britain illustrates the separation. The Gambling Commission lists distinct activities including remote casino, remote casino game host and gambling software. Its remote casino game host guidance says a host does not contract directly with players; players access the games through another operator's site or app. Its software guidance also states that a gambling software licence alone does not permit a business to provide gambling facilities.
That distinction prevents a common procurement error: describing a licensed software or game supplier as the operator of the consumer site. Start with the legal entity named in the site's terms and in the regulator's current register, then verify the domain, product and status. The BETTIMES licence-verification guide gives a repeatable check.
What a white-label casino actually transfers
A white-label arrangement can transfer access to an existing regulated and technical operation. It may also include site templates, games, a Player Account Management system, reporting, customer support, payments and marketing tools. The scope is contractual, not implied by the label.
It does not transfer the licence holder's accountability where the applicable rules keep that responsibility with the licensee. The UK Gambling Commission's current third-party guidance states that compliance for operating gambling websites, including white-labelled sites, sits with the licence holder and cannot be transferred. The licensee needs oversight, controls and due diligence over contracted parties.
For remote licences, LCCP condition 1.1.3 requires contracts for third-party customer interfaces to address compliance with remote technical standards and allow prompt termination for breach, subject to dispute provisions. A brand agreement therefore cannot be assessed only as a design and revenue-share deal.
Before treating a white label as market access, identify:
- the operating licensee and exact licensed activity;
- whether the regulator's register connects the domain to that licensee;
- the entity named in player terms, privacy information and complaints procedure;
- who conducts KYC, AML, safer-gambling, limits, exclusions and withdrawals;
- who contracts with payment service providers and safeguards or reconciles player funds;
- who approves products, bonuses, marketing and material site changes;
- what happens to player balances, records and open complaints when the relationship ends.
The gambling-operator explainer separates the consumer-facing operator from its brands and suppliers.
What a turnkey casino platform actually transfers
A turnkey platform can reduce integration work by combining components that would otherwise be contracted separately. Depending on the offer, that can include front end, PAM, wallet, game aggregation, payments orchestration, reporting, CRM and risk or compliance tooling. It remains a supply arrangement even when the bundle is extensive.
The customer must establish which party makes regulated decisions and which permissions apply. A platform supplier can provide tools for identity checks or transaction monitoring without becoming the entity that decides whether a player may gamble. A managed service can execute a defined process without removing the operator's accountability. The iGaming platform guide explains the main technology layers, while the transaction-monitoring guide covers the difference between an alert and a documented decision.
A credible turnkey proposal should name every included product and dependency. “Payments included” may mean API access rather than an acquiring agreement. “Compliance included” may mean configurable tools rather than licensed operational responsibility. “Full data access” may mean dashboards while raw event exports, documents, model outputs or deletion records remain unavailable.
Control map: documents to verify before signing
Convert the sales proposal into a record-level control map. An accountable owner, legal entity and evidence source should exist for each function.
| Role | What it means | Where to verify |
|---|---|---|
| Licence and domain | Who is authorised for the product and territory, and is this exact site covered? | Regulator register, licence conditions, domain record and legal opinion where needed |
| Player contract | Which entity accepts the player and owes balances, withdrawals and complaint handling? | Terms, account screens, complaint policy and regulator record |
| Payment chain | Who is merchant, acquirer client and settlement-account owner? | PSP and acquiring contracts, descriptors, bank-flow map and chargeback rules |
| Data roles | Who decides why and how each personal-data process occurs? | Privacy notice, processing map, controller or processor analysis and DPA |
| Compliance operations | Who performs and who approves KYC, AML, safer-gambling and sanctions decisions? | RACI, policies, case records, escalation rules and audit access |
| Technology and content | Who controls releases, game approvals, configuration and incident response? | Architecture, supplier list, change log, test evidence and service levels |
| Brand and intellectual property | Who owns the name, domain, creative, content and localisation? | IP schedule, registrar account, brand filings and licence terms |
| Exit and portability | What can be exported, in which format, by when and at what transition cost? | Exit schedule, data dictionary, sample export, deletion terms and assistance plan |
If a proposal cannot answer one row, record the uncertainty instead of assigning the role from a marketing label.
Three markets show why the labels do not travel cleanly
Regulatory roles differ by jurisdiction. The same commercial package may need a different entity, permission and contract structure in another market.
| Role | What it means | Where to verify |
|---|---|---|
| Great Britain | The operating licensee remains responsible for white-labelled sites and third parties; host and software activities are separately licensed | A branded domain or software licence is not itself the customer-facing operating licence |
| Malta | A Gaming Service Licence is B2C; a Critical Gaming Supply Licence is B2B for material game elements or regulatory-record systems | An MGA B2B supplier licence does not make the supplier the B2C operator |
| Ontario | A private operator must register with AGCO and execute an operating agreement with iGaming Ontario before offering games | A platform or supplier arrangement alone does not admit a brand to the regulated market |
The Malta Gaming Authority's licence FAQ distinguishes a B2C Gaming Service Licence from a B2B Critical Gaming Supply Licence. Its B2B guidance covers supply and management of material game elements and software or control systems that process essential regulatory records. BETTIMES explains the boundary in Malta B2C vs B2B gaming licences.
Ontario uses another structure. iGaming Ontario says private operators must register with the AGCO and execute an operating agreement with iGaming Ontario before offering games. Its market-entry steps separately address operator registration, supplier readiness, systems and data checks, and the operating agreement. The Ontario registration guide covers those layers in detail.
These examples do not create a universal model. They show why the target market must be selected before the supply model is approved.
Who owns player data in a white label or turnkey model?
“Data ownership” is too broad to resolve the issue. Separate personal-data roles, database access, intellectual-property rights, retention duties and contractual export rights.
The UK Information Commissioner's Office defines a controller as the party that determines the purposes and means of processing, while a processor acts on a controller's behalf. Its controller and processor guidance explains that the practical decisions and processing relationship determine the role. A provider is not necessarily only a processor for every activity, and the same organisation can have different roles for different processing.
Create a data inventory by purpose: account administration, identity verification, fraud, AML, safer gambling, marketing, analytics, support and regulatory reporting. For each purpose, record controller status, lawful basis, processor chain, location, retention, subject-right handling, security duties and export format. Then test a sample export before launch. Dashboard access is not the same as a complete, documented and reusable dataset.
Payments and player funds need their own map
Neither model tells you who is the merchant of record, contracts with an acquirer, owns settlement accounts or bears chargebacks. Those roles affect onboarding, descriptors, reserves, refunds, reconciliation and exit.
Trace one deposit and one withdrawal from the player's instrument through the PSP, acquirer, bank accounts, wallet ledger and player balance. Name the legal entity at every step. Record currency conversion, fees, failed payments, reversals, chargebacks, withdrawal approvals and reconciliation ownership. If the model relies on the licensee's payment setup, confirm what changes when the brand moves to its own licence or another platform.
Payment coding is also separate from licensing. The MCC 7995 guide explains why a merchant category code, network rule and local gambling restriction answer different questions.
Migration and exit rights can outweigh the launch bundle
The cheapest launch structure can become expensive if the brand cannot move its players, history, domain or integrations. Evaluate exit before negotiating commercial upside.
Require the contract to specify the trigger, notice period and assistance for ordinary termination, regulatory suspension, licence loss, supplier insolvency and material security failure. Define the treatment of player balances, open withdrawals, complaints, self-exclusion records, AML files, consent records, disputes and reporting duties. Some records may need to remain with a regulated entity even when commercial data is transferred.
Test portability with a data dictionary and sample file. Identify stable player and transaction identifiers, document formats, event history, bonus state, game rounds, payment references and audit logs. Document which third-party integrations can be assigned and which need new certification or onboarding.
How to choose between white label and turnkey
The useful question is not which label is better. It is which control profile fits the intended market and the organisation's current capability.
| Role | What it means | Where to verify |
|---|---|---|
| The team needs to validate a brand before building a full licensed operation | A clearly scoped white-label arrangement in an eligible market | No verifiable licensee, domain record, player-contract entity or funds map |
| The business intends to hold the customer-facing licence and build durable operating capability | A turnkey platform with explicit customer control and migration rights | Supplier cannot separate tools from regulated decisions or provide usable exports |
| The team has its own licence and selected components already | Modular platform or managed-service procurement may fit better than either label | Bundle forces duplicate systems, unclear subcontractors or unwanted control transfer |
| The target market has a distinct operator-agreement or licence architecture | Design the legal and supply chain for that market first | Provider treats approval in another jurisdiction as portable permission |
Model total dependency, not only price. Include licensing work, staffing, certification, payments, game approvals, reporting, data access, audit, migration and the cost of replacing the provider. Do not treat a provider's generic launch time or revenue-share range as a forecast for a specific operator.
Questions to ask a white-label or turnkey provider
- Which entity will be the customer-facing licensee in each target market?
- Which exact domains, products and brands will appear in the regulator's records?
- Which entity contracts with players and owes withdrawals and balances?
- Who makes final KYC, AML, safer-gambling, bonus and account-closure decisions?
- Who is merchant of record, and who contracts with the PSP, acquirer and banks?
- Which personal-data roles apply to each processing purpose, including the provider's own analytics?
- Which subcontractors, game hosts, aggregators and cloud services are required?
- Can the operator export all required records through documented fields and stable identifiers?
- Who owns the brand, domain, content, creative, configuration and custom code?
- What happens to players, funds, records and open cases when the agreement ends?
- Which statements are guaranteed by contract, and which are only roadmap or sales claims?
- Which regulator, testing laboratory or independent adviser can verify the material assertions?
Common procurement mistakes
- Assuming the brand name in the header identifies the licensed operator.
- Treating a B2B supplier or software licence as permission to contract with players.
- Reading “compliance included” as a transfer of licensee accountability.
- Accepting dashboard access as evidence of complete data portability.
- Leaving the merchant, settlement accounts and chargeback risk out of the control map.
- Comparing headline fees without the revenue definition, deductions, minimums, reserves and exit costs.
- Using another market's licence or approval as proof of eligibility in the target jurisdiction.
- Delaying domain, data and migration terms until after the platform integration begins.
Refresh policy
BETTIMES reviewed the cited regulator and data-protection sources on 22 September 2026. This guide should be reviewed when a cited market changes its licence or operator-entry structure, when a regulator changes third-party responsibility, or when the ICO replaces the controller and processor guidance currently marked for review.
Frequently asked questions
Is a white-label casino licensed?
The underlying gambling operation may be licensed, but the brand itself is not necessarily the licence holder. In Great Britain, the operating licensee offers the gambling facilities and remains responsible for the white-labelled site. Verify the legal entity, licensed activity, domain record, status and player terms in the relevant regulator's sources.
Does a turnkey casino platform include a gambling licence?
Not automatically. Turnkey describes an integrated supply package, not a universal licence category. The customer may still need its own operating or gaming-service authorisation, market agreement, technical approvals and payment onboarding. Ask the provider to identify the licensed entity and permission for every target product and territory.
What is the main difference between white label and turnkey?
The usual difference is where the customer-facing regulated operation sits. A white-label brand commonly operates inside another licensee's setup; a turnkey customer commonly uses a provider's stack while building or running its own operator entity. Contracts vary, so the licence, player relationship, funds, data and decisions must be checked separately.
Who owns the players in a white-label casino?
“Owns the players” has no precise legal answer. Check which entity contracts with the customer, owes balances, acts as data controller for each purpose, holds marketing permissions and has contractual export rights. These roles can be split. A brand may have commercial rights without controlling the regulated account or all personal data.
Can a casino move from white label to its own licence and platform?
Potentially, but the path depends on regulatory approval, player-contract terms, data roles, payment onboarding, domain control, supplier contracts and migration rights. A move may require new player notices or consents, technical certification and a plan for balances and open cases. Test exports and transition duties before the original launch.