Skip to main content
All insights
Methodology7 minute read

B2B gambling licensing: licences, certification and launch evidence

Separate supplier authorisation, technical evidence and launch conditions with scoped examples from Great Britain, Malta and Alderney.

Published 8 October 2026 · Updated 8 October 2026
By iGaming Atlas Research Desk3 primary sourcesReview cadence: 30 days
Three jurisdiction-specific examples for separating supplier authorisation, technical evidence and launch conditions
Jump to a section

The short answer

  • Define the legal entity, activity, product and destination before checking a licence badge.
  • Supplier authorisation, technical evidence and permission to start operations answer different questions. The applicable authority determines which layers are required.
  • The three examples below preserve UKGC, MGA and AGCC terminology. They do not establish a common licence or permission to supply every jurisdiction.
  • An incomplete evidence record needs a defined follow-up question. It does not automatically establish approval or unlawful activity.

Begin with the activity, not the badge

A supplier's licence is one part of an evidence record. It should not stand for every product the business offers, every destination it serves or every condition that must be met before launch. Start with the narrower question: which legal entity will perform which activity, for which product and in which jurisdiction?

Describe the proposed arrangement in plain language. Is the business developing software, supplying executable games, hosting content, distributing through an intermediary or contracting with players? Identify who controls the relevant systems and who signs each contract. A group name, product name and licence holder may refer to different organisations.

This guide provides a research method and selected examples. It does not assess a particular supplier or replace a review of the rules and decisions applicable to an actual arrangement.

Evidence path

From question to defensible conclusion

1

Begin with the activity, not the badge

2

Licensing and technical assessment answer different questions

3

Five questions for a supplier evidence record

4

Build a record another team can verify

Each step must preserve the jurisdiction, product, entity, source and review date.

Licensing and technical assessment answer different questions

An authorisation record can establish a named holder and an activity. A technical assessment can describe a tested product, version, system or process. Read what each document actually covers before using it in a decision. Neither its title nor a certification logo establishes a broader scope than the supporting record.

The following five questions are an Atlas research framework. They do not imply that every jurisdiction has the same approval structure. Where the authority specifies an assessment body, technical process or separate launch step, record that requirement with its own source. Do not transfer a rule from one jurisdiction into every supplier's checklist.

Five questions for a supplier evidence record

An Atlas research framework for a defined arrangement, not a universal list of legal obligations.

The verification questions are editorial recommendations. Add a legal or technical requirement only when a source applicable to the actual jurisdiction, activity and product supports it.

  • Who is authorised? Locate exact legal holder, authority, reference and activity. Avoid assuming: a group logo identifies the holder.
  • What activity is covered? Locate scope and conditions of the relevant authorisation. Avoid assuming: every function of the business is covered.
  • What product was assessed? Locate product, version and scope of the technical record. Avoid assuming: one report covers all products and future versions.
  • What is needed before launch? Locate applicable operational conditions and completion evidence. Avoid assuming: a licence decision completes every launch requirement.
  • What has changed? Locate dated amendments, decisions and revised records. Avoid assuming: an earlier positive check remains current indefinitely.

Build a record another team can verify

Keep the source observation separate from the conclusion. A register naming an entity for an activity is an observation. Whether that activity resolves a proposed distribution arrangement is a further assessment. A reviewer should be able to follow both without guessing which entity or product the source describes.

Record the source URL and the page or passage supporting each material conclusion, alongside the dated observation. This lets another reviewer check the exact evidence rather than relying on a summary or familiar badge.

For each material conclusion, record jurisdiction, exact entity, activity, product scope, primary source, relevant dates and unresolved questions. Keep the date of an act, its effective date, a documented expiry and the actual evidence review date distinct. Missing fields remain missing until suitable evidence is obtained.

For technical evidence, record the product version and stated limits. For a change, identify the changed entity, activity, product or condition instead of treating every update as a new approval. If a document is private, preserve its handling restrictions; this guide uses public authority guidance only.

  • Write the proposed entity, product, destination and operating model in one review brief.
  • Map each conclusion to the source and scope that supports it.
  • Give every unresolved question a reviewer, next action and completion evidence.
  • Reopen the relevant check when a material change or documented expiry affects the arrangement.

Great Britain: software and host activities

The Gambling Commission's remote gambling software guidance covers manufacturing, supplying, installing or adapting gambling software by remote communication. It also says that a business manufacturing software and providing gambling facilities only through other operators' platforms may be eligible for a host licence.

The host conditions described on that page include holding a gambling software operating licence and having no direct contract with the players using the hosted content. These conditions concern the operating model; they are not an automatic host approval. Atlas rechecked the guidance on 8 October 2026; the page states that it was updated on 1 October. Fees are outside this comparison.

Evidence summary

3

named primary sources

Last editorial review: 2026-10-08. Review target: every 30 days.

Define the legal entity, activity, product and destination before checking a licence badge.

Supplier authorisation, technical evidence and permission to start operations answer different questions. The applicable authority determines which layers are required.

The three examples below preserve UKGC, MGA and AGCC terminology. They do not establish a common licence or permission to supply every jurisdiction.

The visual summary does not replace the linked regulator records below.

Malta: critical supply and approved gaming verticals

The Malta Gaming Authority describes critical gaming supply as a B2B licence with a Malta connection: supply from Malta, to a Maltese person or through a Maltese legal entity. Its guidance covers essential regulatory-record software and control systems, as well as material elements of a game.

More than one gaming vertical can fall within the licence, but the MGA says that those verticals require prior approval. A broad supplier description therefore does not establish that every product, vertical or destination is covered. Match the actual supply and entity to the relevant authorisation and approval record.

Alderney: different responsibilities and a separate operational step

The Alderney Gambling Control Commission describes Category 1 through organising and preparing gambling operations, including player registration and verification, the contractual relationship and player funds. Category 2 concerns executing the transaction, including operational management of the platform within an approved hosting centre. An organisation may apply for one or both categories.

The AGCC also separates licence approval from operational preparation, ending with an approval letter to begin commercial operations. Read these categories in their Alderney context. Category 2 is not a universal synonym for a supplier licence elsewhere.

Define the next investigation

Before relying on a record, check that the entity and activity match the proposed arrangement, the evidence is suitable for the planned date and an unresolved condition has not been mistaken for permission. The result may be a narrower research brief rather than an immediate yes-or-no conclusion.

Continue through the linked Atlas market profiles for jurisdiction context. The research request below uses the existing Atlas enquiry process: specify the entity, product, destination and operating model so that the scope can be assessed. It does not certify compliance or grant an authorisation.

Method, limits and maintenance

Atlas rechecked the three linked authority guidance pages on 8 October 2026 and compared the functions they describe. This is a bounded explanatory comparison, not a review of every law, technical standard, fee, licence holder or market-entry condition in those jurisdictions. The related market profiles have their own evidence dates.

The Research Desk maintenance target is 2 November 2026, with earlier review if a cited authority changes the relevant guidance. Current applicable rules and decisions control if they differ from this explanation. The evidence record is a working method, not a supplier ranking or consumer recommendation.

Turn the evidence into a focused research brief

Send the regulatory question, entities and markets you need reviewed. We can scope a private source review with dated evidence and explicit limits.

Markets, outputs, evidence cut-off and fee are agreed in the written scope.

Primary sources

These links are maintained by the named authority. Open the current source before relying on a status.