A catalogue is the beginning of diligence
A game list tells a product team what an integration may expose. It does not establish who owns each responsibility, which build was evaluated or whether the proposed deployment fits the evidence. Useful diligence follows a chain from the contracting entity to the actual release, with an explicit owner for gaps at every handoff.
This brief proposes an editorial review method. It does not rank suppliers, recommend a vendor or certify a catalogue. No supplier has been assessed, contacted or endorsed as part of this publication.
1. Resolve the entity
Ask for the legal entity behind the contract, the role it performs and the entity behind each regulatory reference. Keep trading names as aliases. The MGA register landing page provides access to its licensee register and URL checker; it is a place to begin a check, not proof about a business mentioned in a sales deck.
Record the exact query, the result date and any ambiguity. If a group contains several entities, do not assume a reference associated with one entity covers every other group member. An unresolved match should remain unresolved in the review record.
2. Trace the deliverable
Request a mapping between the catalogue identifier, supplier game identifier, executable or build version, configurable features and relevant evidence. The mapping should survive a rename. A title displayed to a player is often less precise than the identifier used by an integration or test report.
Synthetic example. A catalogue has “Harbour Cards”, version 4.2; a test report names a different internal identifier and version 4.1. The useful next step is to ask for the version mapping and change assessment. Treating similar names as a match would conceal the gap. Treating them as automatically incompatible would also outrun the available evidence.
3. Read the scope of testing
The Commission’s software technical-standards guidance ties RTS and testing expectations to software made available in reliance on a Commission operating licence, and distinguishes overseas-only supply. Use that context to ask which market and deployment the evidence addresses.
A document title such as “certified” is not the scope. Inspect what was tested, the version, exclusions, report date and assumptions. Ask how configuration changes are evaluated and who decides whether fresh evidence is needed. A release checklist should point to those answers rather than repeat an unsupported approval label.
4. Assign the operational boundaries
| Boundary | Question for the review | Example evidence |
|---|---|---|
| Catalogue update | Who approves a new or changed entry? | Reviewed change manifest |
| Game session | Who owns interruption and reconciliation? | Failure scenario and responsibility record |
| Player control | Where is the decision enforced? | Control trace across services |
| Incident | Who can disable the affected version? | Named role and tested procedure |
| Exit | What remains available after termination? | Retrieval and migration agreement |
These are suggested review questions, not a prescribed contract. Avoid assigning responsibility to “the API” as though a technical boundary were a legal person. Name the organisation, the accountable role and the system that performs the action.
The MGA’s B2B guidance can help frame a discussion of critical supply. It does not settle the classification of an unexamined integration. Record that classification as a separate question for competent review.
5. Make change review repeatable
A useful diligence pack includes a dated evidence index, unresolved questions, accepted assumptions and a review owner. When a catalogue changes, compare the new manifest with the reviewed one. Investigate removed identifiers as well as additions: a disappearance can affect historical evidence and support workflows.
An example acceptance exercise is to withdraw one synthetic game version, verify that new sessions cannot select it, and confirm that historical records remain interpretable. Another is to simulate an unavailable supplier endpoint and check that the operator can explain the resulting user-facing state. Do this in a test environment with synthetic records.
What to carry into a meeting
Bring five concrete items: an entity map, a version map, a test-scope note, a responsibility table and a list of unresolved questions. For each gap, identify the evidence needed and the person who can provide it. A short explicit gap list is more useful than an impressive but untraceable folder of PDFs.
The licensing brief explains the scope layers. Technical recordkeeping covers the evidence trail, and the matrix gives direct access to the source references used here.
Source-backed statements and editorial examples serve different purposes. Verify applicability and the current text before using a source for a legal or release decision.
Source notes
Each note identifies the reading task and its limits. A source recheck does not establish a complete current legal position or change this brief’s original publication date.
GC-SOFTWARE Technical standards for gambling software
Software made available in reliance on a Commission operating licence must meet its RTS and relevant testing strategy. The page distinguishes overseas-only supply.
Source recheck: . Outcome: verified within this task: Deployment scope and distinction for overseas-only supply.
No build has been tested. The complete current testing strategy has not been audited; this page is a reading entry point.
Read the official sourceMGA-REGISTER Licensee Register and URL Checker
The official landing page provides access to the licensee register and URL checker. No particular vendor has been checked here.
Source recheck: . Outcome: verified within this task: Presence of official register and URL-checker entry points only.
No register query, individual entity, licence or domain has been assessed.
Read the official sourceMGA-B2B Game Providers and Back Office
The application guidance describes B2B critical gaming supply, including material game elements and software processing essential regulatory records.
Source recheck: . Outcome: verified within this task: The application page’s description of critical gaming supply.
No specific integration is classified. Application guidance is not a complete legal instrument or proof of authorisation.
Read the official source