Nevis B2B and White-Label Gaming Licences
A Nevis B2B licence covers the relevant supply of gaming services to operators. It does not by itself authorise a player-facing casino or allow a client brand to use the supplier's licence. NOGA treats B2C and B2B separately. White label requires both B2C and B2B licences plus NOGA's prior approval. Before signing a platform agreement, identify the actual operator, supplier, player-contract entity and owner of each domain. MGL Solutions can use that map to assess the application scope and prepare a licensing proposal.
Which category fits the activity?
Classify each company by what it does. Vendor labels such as “turnkey”, “platform” and “white label” do not identify the regulated entity.
Activity | Route to assess | Evidence that resolves the question |
|---|---|---|
Contracting with players and operating the gaming service | B2C | Player terms, domains, payment and operating responsibilities |
Supplying games, software or relevant gaming systems to operators | B2B | Product description, technical control, customer agreements and KYB |
Combining supply with a player-facing operation | Both categories as applicable | Separate activities and contracts for each entity |
Providing a white-label arrangement | Both categories plus NOGA's prior approval | The proposed operator/supplier structure, brands, domains and duties |
Selling access to another company's licence | Sublicensing, which NOGA prohibits | Do not pay for it or claim the licence; a Nevis licence is not transferable |
Section 8 of the Nevis Ordinance distinguishes the classes. Requirements v2 says they carry separate fees and can both appear on the licence when obtained. Multiple gaming forms within a class do not merge B2C and B2B.
Aggregators, developers and affiliates
Requirements v2 expressly asks B2B applicants to describe models such as own games and game aggregation. Map what the developer or aggregator supplies, who uses it and which entity controls it.
An affiliate that only refers traffic is not automatically equivalent to a game supplier. Check whether the business also operates accounts, supplies regulated systems or contracts with players. Get each of those functions classified separately.
Build one responsibility schedule before agreeing the price
Name an accountable entity and contact for each duty, then attach the supporting evidence. Use the schedule to reconcile the application, platform contract and website terms.
Duty | Decision to record | Supporting evidence |
|---|---|---|
Player contract | Who is the player's legal counterparty? | Draft terms, company records, approved scope |
Money | Who receives deposits, controls balances and pays withdrawals? | Funds-flow diagram, merchant and settlement agreements |
KYC, AML and reporting | Who performs checks, resolves exceptions and reports? | Named officers, policies and outsourcing terms |
Games and systems | Who supplies content and handles testing or changes? | Provider agreements, relevant certificates, change process |
Player protection and disputes | Who owns exclusions, complaints and ADR? | Procedures, responsible contacts and applicable engagement |
Markets and affiliates | Who approves countries and acquisition channels? | Market decisions, supplier restrictions, campaign instructions |
Brands and domains | Who owns and operates each approved URL? | Domain evidence, issued approval, register entry |
Changes and exit | Who obtains approval and handles termination, data and balances? | Change/exit clauses and continuity responsibilities |
Before signing, compare this schedule with the application, player terms and payment agreements. Record who accepted each duty and which approval or contract supports it. Leave a duty unresolved if the named party or evidence is missing.
Contradictions count as unresolved too. If the contract assigns player money to one company but the payment agreement names another, fix the conflict before relying on the model. The licence conditions put player KYC, AML and reporting duties on the licensee, whoever performs the task.
What evidence does a B2B application need?
Prepare the shared company and personal file. Requirements v2 adds a B2B document list: a KYB policy, draft B2B agreements, domain ownership, compliant terms and a description of the actual business model. Provide applicable independent RNG/testing evidence for proprietary content and agreements for outsourced content. NOGA's official website describes a 4 to 6 week licensing process. NOGA told MGL in August 2026 that it reviews a complete application in 4 to 6 weeks.
The business plan and financial projections should match how you charge customers and deliver the service. The main Nevis requirements cover personal and corporate documents, officer appointments and source of funds evidence. A business without direct players must still address those shared requirements.
Three checks before launch
Counterparty and domain: verify the exact company, category and relevant URL through the Nevis licence-check workflow.
Market and contract: use the market-review guide to separate supplier permissions, operator obligations and player access.
Operational evidence: reconcile contracts, testing, funds flow, player controls and public licensing statements with the approved arrangement.
The issued approval and applicable law determine what the parties may do.
Request a quote for the defined arrangement
Compare quotes on the same entities, categories, brands and continuing duties. Ask for separate lines for regulatory fees, company setup, officers, application work, testing, platform charges and white-label authorisation. Ask how new domains, delayed approval, changes and exit affect the price.
The Nevis fee breakdown explains published licensing charges. MGL's B2B licensing service compares supplier licences in Malta, the UK, Anjouan and other jurisdictions; white-label casino solutions cover the platform itself.
Send MGL your activity map, responsibility schedule, ownership chart, supplier list, brands, domains and target markets. Request a Nevis scope assessment before you sign an agreement that depends on an unconfirmed permission.
Navigating the gaming license process can be complex. Here's a streamlined guide to each step