Malta B2B Gaming Licence Application: Evidence to Prepare

The MGA system audit compares the staged technical environment with the policies and procedures submitted in the application.

Published 4 min readOfficial sources reviewed

Short answer

  • Start with the supply: Identify the functions, applicant entity and relevant Maltese connection before assembling the evidence.
  • Use the B2B worksheet: Map applicable requirements to documents and explain any N/A response.
  • Reconcile the evidence: Ownership, funding, operating plans and technical descriptions should describe the same proposed business.

For a technology business preparing a Malta B2B gaming licence application, the practical starting point is a precise account of the proposed supply. This guide sets out an internal preparation method. It does not replace the MGA’s official checklist or determine whether a particular business needs a licence.

Define the supply and Maltese connection

Critical gaming supply concerns functions, not a broad commercial label such as “back-office technology.” The Gaming Act defines critical gaming supply as a material supply indispensable to determining game outcomes, or an indispensable component in processing or managing essential regulatory data, or both. Gaming Act, article 2.

The MGA’s B2B guidance identifies relevant software, control systems and material game elements. The statutory licensing rule applies to critical gaming supply from Malta, to a person in Malta or through a Maltese legal entity, subject to applicable exemptions. The distinction matters: “to a person in Malta” is not simply a nationality test. MGA B2B guidance, Gaming Authorisations Regulations, regulation 3 and First Schedule.

Write a service description that a compliance reviewer and an engineer can both use. Identify the functions provided, the customer, the responsible legal entity and the records the system touches. Where classification remains uncertain, separate confirmed facts from the proposed interpretation before carrying that assumption into other documents.

Map the B2B checklist to the evidence

Use the current System Documentation Checklist to build the submission inventory. The MGA advises consulting it before starting an application and requires the checklist and supporting information to be submitted electronically through the Licensee Portal. MGA application instructions.

The workbook linked by the MGA at our check contains separate B2C, B2C with DLT and B2B worksheets. Use the relevant B2B items and read the Introduction. It expressly requires an explanation for an N/A response; some items also contain conditions or exceptions that should not be lost when copying them into an internal tracker. System Documentation Checklist, Introduction and B2B worksheets.

As an internal working method, give each item a document owner, version date, evidence reference and review status. Assign unresolved questions to a responsible person. This distinguishes a missing file from an unanswered question about the proposed operation; the tracker itself is a preparation recommendation, not an additional MGA form.

Reconcile ownership, funding and operating plans

The MGA’s application-process guidance describes reviews of fitness and propriety, funding, business viability, operating procedures and technical implementation. These are connected parts of the assessment, so preparation should connect the ownership explanation to the proposed operation. Application Process Guidance Note, sections 1.2–1.6.

Compare entity names and ownership descriptions across corporate documents, the business plan and supplier arrangements. Check whether the staffing and outsourced services in the operating plan are supported by the resources in the financial model. Where a function depends on a third party, explain who performs it and who oversees it. These cross-checks are practical recommendations, not a claim that every example is a separately prescribed document.

For example, if a supplier agreement names one group company but the architecture assigns the service to another, record the discrepancy and resolve it before submission. A consistent explanation is more useful than separate presentations that cannot be reconciled.

Match system diagrams to demonstrable controls

The B2B worksheet calls for system and application architecture, network information and relevant business-partner agreements. The application-process guidance also describes an external system audit by an independent provider from the pre-approved list, comparing the staged environment with submitted policies and procedures. B2B checklist, sections 7 and 9, Application Process Guidance Note, section 1.6.

As a readiness exercise, map a representative regulatory record from its origin through processing and storage. Identify the responsible service, where another provider enters the process and where control passes between systems. Use consistent names across diagrams, policies and implementation notes.

Walk through that record with engineering and compliance colleagues. Can both teams identify the same system, responsible role and evidence? Can they explain what happens if an external dependency fails or a configuration changes? Record unanswered questions and assign follow-up work. This internal walkthrough is not the official system audit and does not establish compliance.

Check open issues before submission

The following is an internal readiness checklist, not the MGA’s official document list:

  • Confirm the proposed critical supply, relevant Maltese connection and applicant entity.
  • Map applicable B2B checklist items to evidence and explain non-applicability.
  • Reconcile ownership, funding assumptions and operating responsibilities.
  • Trace essential regulatory records and third-party dependencies through the system.
  • Check whether documented procedures match the intended technical environment.
  • Assign owners to open questions and retain a versioned record of changes.

The purpose is to make contradictions visible before submission. Opening an application or accumulating files is not a determination of eligibility or readiness. Licence scope, current requirements and unresolved classification questions still need review against the individual operation.

For the broader distinction between supplying technology and conducting a regulated activity, see prediction-market classification and B2B business boundaries. If the business also supplies the UK market, review the separate UK software and casino game-host licensing framework; the Malta preparation exercise does not answer that jurisdiction’s licensing questions.

Official sources

  1. MGA — Game Providers and Back Officewww.mga.org.mt
  2. MGA — System Documentation Checklist, MGA/F/001 V5 03/23, Introduction and B2B worksheetswww.mga.org.mt
  3. MGA — Application Process Guidance Note, February 2023 v1www.mga.org.mt
  4. Gaming Authorisations Regulations, S.L. 583.05, regulation 3 and First Schedulelegislation.mt
  5. Gaming Act, Chapter 583, article 2 definitionslegislation.mt

Checked on 17 Nov 2026. Rules, fees and forms change; confirm the current position before acting.