Gaming License Requirements and Documents
Gaming license requirements usually cover the applicant company, relevant owners and managers, funding, the business model, and the systems used to operate it. No single document pack satisfies every gambling authority. Build your checklist from the selected license category and the current official application instructions.
)
Applicant due diligence examines the people and money behind the license holder. Player due diligence is a separate operating process, covered by your AML compliance arrangements.
Check eligibility before collecting documents
First identify the proposed license holder, activity, target markets, ownership structure, and funding model. These facts decide which requirements apply. A B2B supplier, a startup casino, and an existing operator entering another market may need different evidence.
Local structure matters too. Do not assume that a company incorporated anywhere offshore meets another authority’s requirements. The Isle of Man application guidance, for example, requires a genuine local presence. That means a Manx company, at least two local directors, and a resident Designated Official or Operations Manager. These conditions belong to the Isle of Man route and do not carry over elsewhere.
If the framework or category is still undecided, return to the licensing jurisdiction hub. A large generic pack will not fix an unsuitable licensing route.
Group corporate, personal, financial, operational, and technical evidence
Use this table as a preparation framework. The authority’s forms decide which items are mandatory, who must provide them, and what alternatives it accepts.
Evidence group | Materials to check for applicability | What the materials should establish |
|---|---|---|
Company and control | Incorporation records, constitutional documents, registers, ownership chart, relevant group records | Who applies and who owns or controls it |
People and suitability | Identity and address evidence, CVs, declarations, references, criminal-record evidence where required | Identity, relevant history, experience, and fitness of people in scope |
Finance and funding | Financial statements or startup forecasts, bank evidence, investment or loan documents, source-of-funds and source-of-wealth records | How the business is financed and whether the explanation is evidenced |
Business and operations | Business plan, product and market descriptions, main contracts, staffing, player terms, applicable policies | What the business will do and how it will be controlled |
Technology and security | System diagrams, supplier details, testing and certification evidence, security controls, technical policies | How the proposed system meets the applicable technical requirements |
The British application document guide lists different items for remote and non-remote applicants and lighter versions for small businesses. Read alongside the MGA application checklists, it shows why the final list must come from the relevant authority and application type.
A startup may rely on forecasts and the proposed funding arrangements where the procedure permits. An established operator may also need historical financial and operating records. Check what evidence the procedure accepts for a new company, which cannot supply a trading history it does not have.
Keep bank and payment-provider requests in a separate register. Their commercial acceptance criteria can differ from licensing requirements. A bank approval does not prove that you meet the authority’s checklist, and a license does not oblige a bank to open an account.
Disclose ownership and control consistently
Trace the structure through intermediate companies to the relevant individuals. Show ownership percentages, voting or other control arrangements, and the relationship between the applicant and operating suppliers. Apply the authority’s own disclosure thresholds and definitions. A threshold from another jurisdiction does not carry over.
Check the chart against registers, shareholder documents, declarations, and the business plan. If names, percentages, or dates differ, explain the discrepancy and correct the underlying record where necessary.
Nominees and corporate shareholders do not remove the need to disclose the people the framework names. Trusts, layered holdings, recent transfers, and unusual control rights may need extra explanation. Record who can provide that explanation before filing.
Prepare the people in scope for due diligence
Identify which owners, directors, key function holders, and other relevant people need forms or supporting evidence. The person signing a declaration should review the answers and the disclosure period, including questions about prior regulatory issues, litigation, insolvency, or criminal history where applicable.
Assess a past issue against the relevant question and framework. Do not leave it out because it seems unrelated, and do not assume that adverse history automatically blocks an application. Give a complete account supported by the available records.
CVs should state real roles and experience. For a compliance or technical appointment, check the person’s eligibility and capacity to do the job. A named role without authority, access, or time weakens the operating plan.
Distinguish source of funds from source of wealth
Source of funds explains the money used for a particular investment or transaction. Source of wealth explains how a person built their broader wealth. The required depth depends on the authority’s questions and the applicant’s circumstances.
For application planning, map the proposed funding from its origin through the contributing person or entity into the applicant. Link the explanation to records such as sale agreements, employment or business income records, investment statements, loan agreements, and transaction evidence as relevant.
An unexplained transfer from an owner’s bank account may leave the original source unresolved. Crypto-derived funding needs a traceable history too. The Gambling Commission’s cryptoasset guidance says it will not consider operating license applications with a crypto funding element without a full and complete source-of-funds history.
If the money comes from a loan, identify the lender, commercial terms, repayment obligations, and any control rights. Reconcile those terms with the financial forecast and ownership disclosures.
Make policies describe the proposed operation
An application policy should identify the trigger, responsible role, action, escalation path, and retained evidence. Relevant subjects can include customer verification, AML, safer gambling, complaints, player funds, information security, and business continuity. Applicability and required detail vary by framework and product.
Compare each policy with the platform and staffing plan. If the policy promises manual review before a transaction, name who performs that review and confirm the system can hold the transaction. If the process depends on a supplier, document the supplier’s role and your oversight.
Use gambling compliance policy support for that work. Keep technical reports and system acceptance criteria in the technical requirements register.
Confirm document validity, certification, and translation rules
Do not apply a universal “three-month validity” or apostille rule. For every document type, check the current instructions on age, certifier, certification wording, language, translation, legalization, and delivery format.
Order documents with external lead times first, but do not obtain short-validity evidence so early that it expires before submission. Record the instruction that applies to your file; another applicant’s past experience may reflect older rules.
Use a readiness register to decide whether to submit
Requirement | Evidence and version | Owner | Remaining gap | Ready when |
|---|---|---|---|---|
Applicant eligibility | Entity records and category assessment | Legal lead | Local appointment unresolved | Required structure and appointments confirmed |
Ownership disclosure | Chart and supporting registers | Corporate secretary | Historic transfer needs explanation | Records and declarations reconcile |
Funding | Narrative and transaction trail | Finance lead and funder | Origin record missing | Explanation is supported from origin to applicant |
Operating controls | Policies and implementation evidence | Compliance lead | Escalation owner unassigned | Process has an accountable owner and usable tools |
System evidence | Version-specific reports and diagrams | Technical lead | Lab scope not agreed | Applicable technical evidence is complete |
The entries above are illustrations. Replace them with the actual requirements and gaps in your file.
A document count is a weak readiness test. A stronger one: every applicable requirement has matching evidence, and you have resolved material inconsistencies. If you cannot supply a required item, ask the authority what alternative it accepts. Do not leave the item out silently.
Follow the five-stage application workflow once the pack is ready. If inconsistencies have already generated questions, use the application mistakes guide.
Request a document readiness review from MGL. Send the proposed jurisdiction, license category, ownership outline, and current checklist through a secure channel we agree with you. Do not send sensitive identity documents with a first general inquiry.
Rate This Article
Your feedback helps us improve our industry research and publish more useful insights for operators and founders. By sharing your opinion, you help our team better understand what topics matter most to professionals in the iGaming industry.

