How software developers and platform providers benefit from a Nevis B2B license

A gaming platform may not accept player bets and still fall within the regulated B2B perimeter. The decisive factor is its function: the software may manage gaming sessions, calculate outcomes, process balances or transmit betting data. Operators and regulators therefore distinguish such a supplier from an ordinary IT contractor. A Nevis B2B licence formalises its role within the regulated structure but does not replace technical certification or authorise B2C operations. This article examines the commercial and legal benefits the licence offers software developers and platform providers.

Which software businesses fall within the B2B licensing perimeter

NOGA links a B2B licence not to a company’s general technology status but to the supply of products and infrastructure for gaming operations. The regulator’s official website includes gaming software developers, platform and infrastructure providers, and white-label solutions within this category.

The B2B perimeter may cover:

• Game studios developing slots, table games or other proprietary content;
• RNG and game engine developers whose technology determines or processes gaming outcomes;
• Casino platforms managing sessions, wallets, balances, bonuses or game integrations;
• Sportsbook providers supplying betting engines, odds management, settlement logic or data-feed integrations;
• Aggregators connecting operators with multiple game suppliers;
• Live gaming providers controlling studio infrastructure and content transmission;
• White-label and turnkey providers supplying operators with ready-made technical and operational environments.

Working with a gaming company does not automatically require licensing. Corporate website development, general cloud hosting, design or routine technical support may fall outside B2B gaming activity where the supplier does not control critical functions.

Classification depends on whether the software affects stakes, outcomes, player balances, gaming records or platform operations. Relevant factors also include access to the production system, the ability to modify critical code and the supplier’s role in supporting the operator.

A product’s commercial name is not decisive. A SaaS platform may perform regulated gaming functions, while a standalone analytics tool may remain ordinary B2B software. The product scope should therefore be defined before incorporating the Nevis company and submitting the application.

What commercial value the licence creates

For a software supplier, the value of a B2B licence lies not in using a regulator’s logo but in negotiations with operators and their compliance teams. It shows that a separate Nevis entity has undergone corporate and personal due diligence, disclosed its ownership and submitted evidence for the declared product.

Practical benefits may include:

• Clear regulatory status. Clients can identify the company supplying the gaming technology and the basis for its B2B activity.
• Structured supplier onboarding. Information on owners, management, source of funds and the product has already been prepared for NOGA.
• Dedicated contracting entity. Agreements with operators, platform providers and content suppliers can be consolidated within the licensed company.
• Evidence of product rights. The application file connects the applicant with its software, domains, RNG certificates and external content agreements.
• Support for international sales. The licence may matter to clients unwilling to engage an unregulated critical supplier.
• Partner transparency. The company’s status can be checked in the NOGA public register.

The licence can also separate functions within a group. The B2B company owns or supplies the technology, while the B2C operator contracts with players and manages player-facing operations. Agreements, payment flows and technical architecture must support this distinction.

Commercial value still depends on the client and market. A Nevis B2B licence does not require foreign operators, banks, payment providers or regulators to accept the supplier. Before applying, the company should confirm whether prospective clients recognise the licence and require additional certificates or approvals.

What a Nevis B2B licence does not permit

A B2B licence regulates the supplier’s activities; it does not make the company a gaming operator. The distinction depends on the player relationship. If a company registers customers, accepts bets, maintains player balances or pays winnings, a supplier licence alone is insufficient.

The licence does not allow the supplier to:

• Conduct B2C operations in its own name;
• Permit other companies to operate under its licence;
• Transfer the licence to another legal entity;
• Serve every market without reviewing local law;
• Replace product testing with the company’s regulatory status;
• Extend the authorisation to all group entities.

NOGA guidance states that sublicensing is prohibited, and the licence is issued to a specific Nevis entity following due diligence on that entity.  A platform provider therefore cannot sell “access to its licence” as a standalone product. Each B2C operator needs its own legal basis for serving players.

White-label structures require separate assessment. Where one company supplies the technology and another manages the brand and player-facing operations, each party’s role must be defined. NOGA guidance provides for both B2B and B2C licences and prior regulatory approval for this model. The agreement must not disguise the transfer of operator functions to an unlicensed company.

A B2B licence also does not replace RNG certification, game testing or sportsbook integration review. It confirms the supplier’s status, while a technical report covers specific software, versions and configurations.

Nevis authorisation does not compel a foreign regulator to recognise the supplier. Before contracting, the company must examine the rules governing the B2C operator and its player markets. Some jurisdictions may require a local supplier licence, registration or product approval.

Product evidence required for software and platforms

NOGA must establish both who owns the applicant company and where its product comes from. The licensing file should identify who developed the technology, who owns the rights and which third parties support its operation.

Under the NOGA requirements, a B2B applicant must provide proof of domain ownership, a KYB policy and draft agreements with business clients. Independently developed software requires RNG testing certificates. Where third-party games are used, the applicant must disclose the relevant game and content provider agreements.

Documents must relate to the product version actually supplied. A certificate for the underlying RNG does not automatically cover the full platform integration or a new game build. Likewise, a developer agreement does not prove commercial distribution rights unless it addresses IP ownership and licensing.

Before applying, the supplier should prepare a product map identifying components, owners, laboratories, suppliers, versions and related agreements. This review can reveal inconsistencies between the business plan, technical architecture and product rights before regulatory assessment.

Corporate, ownership and KYB requirements

A B2B application covers two subjects: the company receiving the licence and the product it supplies. An existing foreign software company cannot act as the applicant because the licence is issued to a Nevis-registered entity. The foreign company may remain a shareholder or IP owner if those relationships are properly documented.

The corporate file generally includes:

• Certificate of Incorporation;
• Articles of Incorporation and By-Laws;
• Certificate of Incumbency;
• Certificate of Good Standing for a company older than one year;
• Details of directors, shareholders and UBOs;
• A signed organisational chart;
• Parent-company documents tracing ownership to natural persons;
• ;
• Evidence of source of funds and source of wealth.

Corporate documents must be notarised, and certificates of incumbency and good standing must be issued within the last three months. Equivalent documents are required for parent companies and corporate directors. 

Individual files include a passport, proof of address, criminal background check, CV and required references. Names, addresses and ownership percentages must remain consistent across all documents.

A B2B applicant must also submit a KYB policy and draft agreements with prospective operator clients. The KYB procedure should explain how the supplier verifies the client’s licensing status, ownership, target markets and eligibility to receive the product. Contracting without these checks may expose the supplier to an unlicensed operator or one serving markets unlawfully.

The application also requires a business plan signed by a director. It must include three-year financial projections with stated assumptions, a cost breakdown, projected P&L and cash flow statements, and all funding sources. It must also identify key suppliers and platform providers, summarise internal policies and describe the regulatory compliance framework. For a software supplier, this section should match the product map, IP agreements and B2B contracting model. 

NOGA's current requirements list two mandatory appointments without limiting them to B2C applicants: an independent Compliance Officer and a local Reporting Officer. The Compliance Officer cannot be a director, shareholder or UBO and must have relevant industry experience or qualifications; the function may be outsourced if the provider designates a specific individual. The Reporting Officer must reside in Nevis and be registered with the FSRC. Beyond these appointments, a B2B supplier needs clear internal responsibility for KYB, regulatory changes, technical documentation and client oversight. 

Fees, timing and ongoing regulatory costs

The B2B licence cost should be calculated separately from the product development and launch budget. The initial licence fee is €28,000, with a further €28,000 payable annually for renewal.

Additional charges may arise when expanding or changing the structure:

• €750 per additional URL during a licensing cycle;
• €35 per subdomain when adding up to 49;
• €15 per subdomain when submitting 50 or more together;
• €1,000 for due diligence on a new director, shareholder or UBO;
• €5,000 for a material ownership change.

B2B and B2C licences are separate authorisations. If a group or white-label structure requires both, each needs its own application and fees. Listing both categories on one licence document does not combine their functions or costs.

The NOGA website indicates an estimated licensing period of four to six weeks. This assumes a complete file and is not guaranteed. Complex ownership, unverified IP rights or missing technical evidence will extend the review.

The full budget also covers Nevis company formation, a registered agent, Compliance Officer and Reporting Officer services, notarisation and certified translations, accounting, legal preparation, software testing and corporate maintenance.  After licensing, costs include renewals, certificate updates, B2B client oversight and regulatory work on material changes.

The application fee is not the full cost of market entry. The supplier must fund both licensing and continued maintenance of current product documentation. Otherwise, the licence may remain valid while the software version actually supplied falls outside the reviewed regulatory file.

When the licence is commercially justified

A B2B licence is commercially justified when it supports a specific sales objective or regulatory access. Obtaining one merely to enhance the company’s status is inefficient: annual fees and related costs should reflect expected contracts and client requirements.

The case for applying is stronger where:

• The software affects game outcomes, bet settlement, sessions or player balances;
• The company supplies several independent operators;
• Prospective clients accept only licensed critical suppliers;
• The applicant owns or contractually controls the technology and IP rights;
• RNG, games or sportsbook components are ready for independent testing;
• Ownership and funding can be fully disclosed;
• Projected revenue covers licensing and ongoing compliance costs.

The position differs where the product remains a prototype. Without stable architecture, relevant certificates and a defined contracting model, the applicant may struggle to demonstrate what it intends to supply. Incorporating in Nevis before documenting IP rights may also separate the applicant from the actual software owner.

Intragroup use requires separate analysis. If the technology serves only one related B2C operator and is not offered externally, the need for a standalone B2B licence should be assessed against its functions and NOGA rules. Supplying independent operators changes that assessment.

Before applying, the supplier should obtain feedback from potential clients. Their onboarding requirements show whether they recognise a Nevis B2B licence, which testing laboratories they accept and whether local approvals are also required. This commercial validation helps avoid paying for a licence that does not open the intended sales channels.

How Key2Law supports Nevis B2B suppliers

For a software supplier, preparing for NOGA begins not with the application form but with aligning three elements: technology ownership, product functions and the entity that will sign B2B contracts. Key2Law team structures these elements before the licence fee is paid and the file is submitted.

Depending on the project, the work may involve:

• Determining whether the product falls within the B2B licensing perimeter;
• Incorporating the applicant company in Nevis;
• Designing the ownership and operational structure;
• Documenting relationships between the IP owner, developer and licensed supplier;
• Preparing the business plan and software model description;
• Assembling corporate and personal due diligence files;
• Developing a KYB policy for operator clients;
• Reviewing platform, game supply and data feed agreements;
• Matching RNG certificates to actual product versions;
• Drafting B2B contracts and allocating regulatory responsibilities;
• Coordinating the application and responses to NOGA;
• Supporting renewals and material changes.

Document consistency is central to the application. The organisational chart, IP agreements, technical architecture and commercial contracts must reflect the same operating model. If the applicant declares a proprietary platform while another group entity owns the code without a licence agreement, both the regulator and prospective clients will seek clarification.

If you plan to license a game studio, sportsbook technology, aggregator or gaming platform, contact Key2Law before transferring IP or incorporating the Nevis entity. We will help assess whether the licence is commercially justified, identify the required evidence and prepare a structure suitable for both the application and operator onboarding.

_______________________________________________________________________

This article is provided for general informational purposes and does not constitute legal, tax or financial advice. Applicable requirements depend on the jurisdiction and specific circumstances; professional advice should be obtained before making legal or business decisions.