Sports Betting License
A framework for remote and retail betting permissions, operator and supplier roles, product scope, integrity duties, testing conditions, changes and surrender.
A sports betting license is permission for a defined legal entity—or, where the authority expressly permits it, defined covered group entities—to perform defined betting activities under defined conditions. It is not a portable badge for every country, channel, product, brand, supplier, event, or website. The first licensing task is therefore classification: who contracts with the bettor, where the bettor and equipment are located, whether betting is remote or retail, which products are offered, and which other companies control software, data, trading, payments, or regulatory records.
This guide turns that classification into a licensing and application plan. It covers consumer-facing and B2B roles, fixed odds, pools and exchanges, real and virtual events, data and trading supplier boundaries, integrity duties, pre-license testing conditions, key people, required control policies, continuing reports, material changes, and formal exit status. It deliberately does not quote a universal fee or approval schedule because neither exists.
Great Britain, Malta, Ontario, and Ireland use materially different licensing structures. Their inclusion does not rank those markets, establish that an applicant qualifies, or authorize service anywhere else. Check the current law, application requirements, register, product approvals, and technical rules for the exact entity and launch configuration before relying on any route.
Use the start-sportsbook guide for data-chain architecture, ledger design, detailed AML and responsible-gambling implementation, component testing, go-live, continuity, and supplier export. This page stays focused on the sports-betting authorization, product and role boundaries, application evidence, licensing conditions, changes, and formal exit status.
- + Start with the player market, contracting entity, product, channel, and equipment location; do not start with a license seller's package name.
- + Separate the customer-facing operator from hosts, intermediaries, software suppliers, data providers, and managed trading services.
- + Treat fixed odds, pools, exchanges, virtual events, in-play betting, and retail terminals as separate permission questions unless the applicable framework expressly combines them.
- + Map every event-data source, trading decision, bet-acceptance record, settlement source, and integrity escalation to a named owner.
- + Build the application from the production operating model, ownership, funding, key people, system map, policies, and tested controls—not from generic templates.
- + Keep AML, responsible gambling, payments, player funds, and open-bet liabilities distinct even when one platform displays them through a single account balance.
- + Classify each system and change against the local testing rules; a supplier certificate or general standard is not automatic approval for production.
- + Plan reports, notifications, ownership and supplier changes, suspension, surrender, and any locally applicable customer or liability steps before launch.
Continue the decision
Continue with the guide that matches the next licensing, market-access, procurement, or launch decision.
Classify the jurisdiction, product, and channel first
The phrase “sports betting license” hides different legal structures. Great Britain separates remote real-event betting from virtual-event betting and analyzes who is party to the bet, whether remote communication is used, and whether premises permission is also needed. Malta groups fixed-odds betting, including live betting, under Type 2 and pool betting, including exchanges, under Type 3; the application must also specify a remote, land-based, or combined channel. Ireland has separate in-person betting, remote betting, and remote betting intermediary licenses. Ontario's competitive internet market requires both AGCO operator registration and an operating agreement with iGaming Ontario before a private operator enters that market.
Build a separate jurisdiction matrix because none of those permissions automatically covers every sport, competition, bet type, location, brand, or delivery route. Record the player-location rule, regulated activity, license or registration holder, channel, key equipment, product category, website or brand treatment, premises dependency, and separate approvals in one versioned scope document.
For a retail route, classify the operating activity, premises permission, any remote component, self-service betting terminals, device approval, cash and ticket handling, and staff or personal-license dependencies under the selected framework. In Great Britain, an electronically communicated terminal bet can still be remote even when the customer stands inside licensed premises.
| Jurisdiction example | Legal classification | Boundary to preserve |
|---|---|---|
| Great Britain | Great Britain separates remote real-event betting, virtual-event betting, intermediary activity, remote communication, non-remote activity, and premises requirements. | A real-events permission is not a virtual-events permission. A retail location does not by itself make an electronically communicated bet non-remote. |
| Malta | Under Malta's B2C framework, virtual sports games fall under Type 1, fixed odds and live betting under Type 2, and pools and exchanges under Type 3. Applicants must select remote, land-based, or both where applicable. | A product marketed as virtual sports is not automatically Type 2. Approval of a license also does not remove prior vertical approval or convert one gaming type into another. |
| Ontario | An internet operator completes separate AGCO and iGaming Ontario steps, including registration, control implementation, systems and data readiness, and an iGO operating agreement. | This is an Ontario internet-market example. It does not establish a retail permission or authority elsewhere in Canada. |
| Ireland | Ireland has separate B2C license categories for in-person betting, remote betting, and remote betting intermediary activity. | The current application phase and product categories must be checked at filing; a future combined route is not a current approval. |
Jurisdiction-specific boundary
Each jurisdiction row applies only to its named regulator, entity role, activity, product, and channel. It is not a market-access opinion, passport, endorsement, or substitute for the law where the bettor is located.
Separate B2C, host, intermediary, and B2B roles
The entity that contracts with the bettor and owes the customer obligation is not automatically the entity that builds or hosts the system. Great Britain separates providing betting facilities, acting as a betting intermediary, hosting through another operator, and manufacturing or supplying gambling software. A gambling software license does not itself permit the holder to provide gambling facilities to consumers.
Malta draws the boundary differently: a B2C Gaming Service License covers offering the gaming service, while a B2B Critical Gaming Supply License covers material game elements and software or control systems that generate, capture, control, or process essential regulatory records. In Ontario, supplier functions can trigger registration and technology-certification work alongside the operator's entry process. Map the real function and legal responsibility; do not infer it from “white label,” “turnkey,” “platform,” or “managed sportsbook.”
| Role | Core licensing question | Evidence to retain |
|---|---|---|
| Customer-facing operator | Which entity is party to the bet, accepts the customer obligation, holds the account relationship, and offers the regulated product in the target market? | Exact legal name, active permission, approved activity and channel, brands or domains, customer terms, complaint route, and live register entry. |
| Host or intermediary | Does the entity host facilities without a direct customer contract, or bring betting parties together without taking liability for their bets? | Contract flow, customer-facing entity, liability owner, platform access path, host or intermediary permission, and restrictions on direct customer activity. |
| Software or critical supplier | Does the supplier manufacture, supply, install, adapt, manage, or control software or essential regulatory records that require a local B2B permission? | Supplying entity, product and version, regulated function, B2B or software permission, operator clients, hosting, subcontractors, and production configuration. |
| Data or managed trading provider | Is the service only an input or recommendation, or can it create markets, set prices, accept or reject bets, suspend betting, grade results, or alter liability? | Decision rights, source data, limits, override rights, bet-response meaning, audit records, incident access, integrity duties, and any locally required registration. |
| Testing laboratory or assessor | Which components and changes require independent certification or assurance, and which body must recognize the assessor? | Approved laboratory status, test scope, jurisdictional standard, software version, configuration, exceptions, report, certificate, and regulator submission. |
Sources for this section: [1], [2], [3], [7], [13], [14], [20], [23]
Define the licensed product and integrity annex
A license label is not an event catalog. Great Britain's remote real-event permission excludes virtual events, while Malta places fixed odds and live betting in a different gaming type from pools and exchanges. Before filing, create a product register that identifies real or virtual events, fixed odds or pool mechanics, exchange or intermediary activity, in-play use, bet and market families, event classes, customer rules, and the person who approves each item for each jurisdiction.
Treat data and trading providers here only as licensing dependencies. Record whether their functions affect supplier permission, approved systems, essential regulatory records, event approval, or the license holder's reporting duty. IBIA's voluntary Data Standards and GLI-33 can structure provenance and system evidence, but neither document grants permission or replaces the selected regulator's product and integrity rules.
In Ontario, AGCO Standard 4.32 requires sport and event betting operators to mitigate insider-betting and event-manipulation risk, identify unusual or suspicious activity, and report through an independent integrity monitor. Standard 4.34 sets criteria for offered bets, including verifiable outcomes, independent processes, governing-body and integrity safeguards for sports, and specific prohibited categories. Those requirements are Ontario-specific; they are not a universal event list.
| Annex item | Licensing question | Evidence boundary |
|---|---|---|
| Product and channel | Which permission covers the real or virtual event, fixed-odds, pool or exchange model, in-play use, and remote or retail channel? | Keep the exact activity, product or vertical approval, conditions, rules version, and regulator source. A marketing category is not a legal classification. |
| Events and bet types | Does the framework approve events individually, publish criteria or prohibitions, or put the initial classification on the operator? | Record the applicable criteria and decision owner. Ontario Standard 4.34 is an Ontario example, not a universal list. |
| Integrity reporting | Which licensee or registered supplier must identify, preserve, escalate, and report unusual or suspicious activity, and to whom? | A supplier alert is input evidence. It closes the license holder's duty only when the selected rule and report path say it does. |
| Data and trading suppliers | Do their functions create a local supplier role or control essential records, event approval, bet acceptance, suspension, or settlement evidence? | Use contracts and technical standards to describe the evidence and decision rights, not as proof of market permission. |
No universal event coverage
A sports betting, Type 2, software, data, or testing approval does not by itself prove that every sport, league, participant group, event, market, wager type, or data source may be offered. Keep an approval record for the exact catalog used in production.
Sources for this section: [1], [2], [8], [13], [18], [21], [22], [23], [24]
Prepare the application and key-person file
Build the application around the business that will actually operate. A British application can require ownership and group structure, funding and forecasts, management, policies, rules, supplier details, an operational model, system diagrams, and the end-to-end path from registration to payout, with different materials for remote and non-remote operations. The exact file differs by regulator, so use the checklist for the selected route rather than copying this list as a universal form.
Key-person work belongs on the same critical path. In Great Britain, specified management functions require a Personal Management License. Malta requires approval and evidence of qualifications or experience for relevant key functions and has separate processes for changes, additions, and terminations. A consultant, nominal title, or outsourced service does not remove the need to identify who actually controls the licensed activity and whether that person needs approval.
| Workstream | File to prepare | Consistency test |
|---|---|---|
| Entity, ownership, and funding | Applicant and group charts, controllers and beneficial owners, corporate records, funding sources, agreements, financial statements, forecasts, and assumptions. | Every owner, lender, funder, controller, and related entity matches across the forms, contracts, accounts, declarations, and operating model. |
| Business and product model | Player markets, products, channels, brands, customer contract, rules, commercial model, responsible owners, complaints, and regulated dependencies. | The application describes the same product register and liability model that the production contracts and customer terms implement. |
| Systems and suppliers | Operational model, key equipment, system and data-flow diagrams, end-to-end registration-to-payout flow, software suppliers, hosting, payments, identity, geolocation, trading, and support. | Every system and third party has a legal entity, location, contract, permission decision, system of record, failure path, and accountable applicant owner. |
| Policies and control evidence | AML and risk assessment, responsible gambling, customer verification, integrity, complaints, information security, testing, incident, payments, funds, change, and closure controls. | Each policy must define the process, system, data, decision point, responsible role, evidence retained, exception path, review cycle, and applicable legal or technical basis. |
| Key people | Role map, job authority, personal applications or declarations, identity and probity documents, qualifications, experience, conflicts, time allocation, deputies, and succession. | The approved person is the person performing the function; titles, reporting lines, access, decision rights, and outsourced support all agree. |
| Official verification | Direct regulator correspondence, submission receipt, approval letter, license conditions, live register entry, approved domains and activities, and unresolved conditions. | A pending application, copied certificate, sales proposal, or logo is never stored as an active permission. |
Sources for this section: [4], [5], [12], [13], [15], [16], [17]
Prepare the control policies required for the application
The application file must keep AML, responsible gambling, payment and player-funds material in the categories used by the selected authority. Under the MGA framework, a risk-based AML approach, business risk assessment, customer-acceptance policy, approved MLRO, player-protection tools and monitoring, player-funds reporting, and payment-method, PSP and bank-account notifications are separate workstreams. Ontario's entry process likewise separates AML, financial, bank-due-diligence, funds-transfer, and control-readiness work.
Do not import one jurisdiction's fund definition into another. The UKGC's customer-funds framework excludes money staked in open bets from that defined category, while the MGA player-funds report includes open bets and pending withdrawals in its coverage calculation. The license file should state the selected rule and show which ledger components and evidence feed the required report; detailed ledger and control design belongs in the start-sportsbook guide.
| Application file | Licensing question | Scope boundary |
|---|---|---|
| AML and customer risk | Which risk assessment, customer-acceptance policy, MLRO or responsible person, procedures, systems, records and filings does the selected authority require from this applicant? | Use the local law and application checklist. Malta's requirements do not create a universal AML pack for other jurisdictions. |
| Responsible gambling | Which tools, exclusions, limits, monitoring, intervention, training and retained evidence must the application or license conditions describe? | Record the rule, policy version, system owner and evidence promised to the authority; design the full operating flow in the launch guide. |
| Payments | For the selected framework, must the operator disclose or obtain approval for payment methods, PSPs, banks or accounts, and which later changes require notice? | Ontario requires bank-due-diligence and funds-transfer work, while Malta applies specific change notifications. Neither framework is a universal payment-control checklist. |
| Player funds and open bets | Which locally defined amounts must be protected, disclosed, reconciled or reported, and how does the rule treat open bets and pending withdrawals? | Retain the local definition, account and ledger mapping, report and supporting reconciliation without treating the GB or Malta example as portable. |
A provider does not erase the operator boundary
A KYC, AML, payment, wallet, or safer-gambling provider can support the application and licensed operation. The applicant still needs to show the locally required accountability, evidence access, oversight, exceptions, and reporting path. The separate start-sportsbook guide covers implementation and continuity design.
Meet pre-license testing and approval conditions
Testing conditions follow the jurisdiction, license, component, product, and change. UK remote operators and gambling software licensees must meet the applicable Remote Gambling and Software Technical Standards and the testing rules for covered remote products. In Ontario, games and supporting critical gaming systems require certification by an AGCO-registered independent testing laboratory where the rule applies, together with technology-compliance confirmation. Malta includes technical-document review and a staged system audit in its application path.
GLI-33 is an event-wagering system test-scope benchmark, not a license or automatic local approval. Before issue or launch, the licensing file should identify the rule creating each assurance requirement, the accepted assessor, exact system and version, submitted report, exceptions, authority response, and any condition still open. Component inventory and end-to-end production testing stay in the start-sportsbook guide.
| Framework | Pre-license question | Evidence boundary |
|---|---|---|
| Great Britain | Which RTS provision, testing stage, independent report, security audit or change classification applies to the exact remote or software activity? | Retain the governing rule, product and version scope, testing outcome, and submission status. Successful testing does not add a licensed activity. |
| Ontario | Which games, supporting critical gaming systems and suppliers require AGCO registration or ITL certification, and has technology-compliance confirmation been completed? | Some Ontario suppliers require registration and certification. Do not extend the requirement to every supplier or component. |
| Malta | Which technical documents, staged environment and system audit are part of the selected B2C or B2B application and approved verticals? | Record the audit and authority decision for the submitted setup; do not treat it as approval of later changes or another market. |
| GLI-33 reference | Has the regulator adopted or accepted this version and scope, and which production components and operational controls remain outside the laboratory report? | GLI-33 leaves public policy and permitted events to regulators and separates laboratory testing from operational audit. |
No universal laboratory rule
Do not claim that every component or release always needs independent certification, or that a supplier certificate always satisfies the regulator. Classify the exact system and change under the current local testing and approval rules.
Operate, report, and control every material change
The license file becomes an operating calendar after approval. In Malta, that calendar can include B2B client reporting, player-funds reporting, financial and audit submissions, go-live declarations, outsourcing notifications, security incidents, and suspicious-betting reports. Ontario's onboarding includes regulatory-submission channels and notification training. Treat every recurring return, event-driven notification, regulator request, and supporting reconciliation as a control with an owner, source system, reviewer, due rule, submission receipt, and correction path.
Change control is part of licensing, not only software delivery. Malta applies approval and notification routes to changes in technical setup, entity details, policies, terms, payment methods, directors, beneficial owners, funding, and key functions. Great Britain has a separate corporate-control process under which the license may need a continuance application or surrender. Before a product, supplier, owner, key person, payment route, brand, domain, market, system, or control changes, identify every approval, notice, test, contract update, customer communication, and register update that may be triggered.
| Change | Licensing analysis | Release evidence |
|---|---|---|
| Owner, controller, director, or key person | Does the change require prior approval, personal filings, source-of-wealth or funding evidence, a continuance process, notice, replacement coverage, or updated organization charts? | Regulator filing and response, due-diligence record, role and authority map, handover, access change, conflicts, and active-register check. |
| Product, channel, brand, domain, or market | Is the activity already authorized for that entity and channel, or is a new application, variation, vertical approval, premises permission, or local-market route required? | Updated scope matrix, official source, approval, customer terms, rulebook, product register, domain or brand record, test result, and launch gate. |
| System, feed, trading service, or supplier | Does it alter essential records, event or market controls, bet acceptance, settlement, security, data location, outsourcing, B2B licensing, or test scope? | Updated architecture and risk assessment, supplier permission, contract, data flow, test classification, reports, approvals or notices, migration, monitoring, rollback, and exit export. |
| Payment method, bank, PSP, or funds account | Does the change affect the approved payment route, AML risk, player-funds structure, reporting evidence, customer terms, or notice requirements? | Contract, bank or PSP due diligence, payment and data flow, risk decision, regulator filing, reconciliation test, customer communication, and updated funds report. |
Sources for this section: [1], [7], [10], [12], [13], [15], [18], [19], [20]
Record suspension, surrender, and regulatory exit
Suspension, surrender, lapse, and operational closure are different states. In Great Britain, the closure process covers customer communication, complaints and ADR, open and ante-post bets, customer funds, registration cutoff, returns, and surrender. A B2B supplier, inactive license, insolvency event, partial surrender, or another jurisdiction may follow a different route, so start with the holder's exact license and the local trigger.
The exit file should identify the records and liabilities that the selected framework requires the holder to retain, transfer, reconcile, report, or make available. It should also include the authority decision or acknowledgment where one is issued, any status that occurs by operation of law, the effective date, outstanding conditions or returns, and the resulting live-register status. Detailed supplier exports and operational shutdown belong in the start-sportsbook guide.
- 1Classify the trigger and holder
Determine whether the event is a temporary suspension, activity or channel surrender, full surrender, insolvency consequence, expiry or another legal status, and whether the holder is a consumer operator, host, intermediary or supplier.
- 2Identify applicable customer obligations
For an active consumer-facing sportsbook, identify the local requirements for customer notices, registration and bet cutoffs, open and ante-post bets, funds, complaints, outstanding returns and records. Do not impose this consumer checklist on a role that has no players.
- 3Confirm the resulting status
Retain the filing, decision or acknowledgment where one exists, record any status arising by law, settle outstanding regulatory submissions, and reconcile the authority's register with the license copy, domains, suppliers and internal permission records.
Surrender is jurisdiction-specific
Do not copy the Great Britain process into another jurisdiction. Use it as a checklist prompt, then replace every trigger, deadline, approval, funds treatment, record obligation, customer notice, and surrender step with the selected regulator's current requirements.
FAQ
Is there one sports betting license that lets an operator accept bets worldwide?+
No. Great Britain, Malta, Ontario, and Ireland each classify entities, products, channels, and market participation differently. A permission in one framework does not by itself establish authority where another bettor is located. Build and maintain a separate legal and regulator-backed scope for every target market.
Can a sportsbook platform's B2B or software license cover the consumer operator?+
Not by itself. In Great Britain, a gambling software license does not permit providing gambling facilities. Malta likewise separates B2B critical supply from B2C gaming service. Identify the entity that contracts with the bettor and verify its active operating permission separately from every supplier approval.
Does an online license also cover betting shops and self-service terminals?+
Do not assume it does. Great Britain analyzes remote communication, the operating activity, and premises permission separately; an electronic terminal in a shop can involve remote betting. Ireland has separate in-person and remote betting licenses. Document the complete retail transaction and check the local operating, premises, terminal, cash, ticket, and staff requirements.
Does a fixed-odds sports betting permission cover virtual sports, pools, and exchanges?+
There is no universal answer. Great Britain's current remote real-events activity excludes virtual events. Malta places virtual sports games in Type 1, fixed odds and live betting in Type 2, and pools and exchanges in Type 3. Verify each product, mechanic, event category, and channel against the selected regulator's current approvals before it enters the catalog.
Who is responsible for sports data, trading, and integrity reports?+
The contracts and license map must name separate owners. A data provider may source events, a trading service may recommend or make price and risk decisions, and an engine may accept and settle bets. The licensed operator still needs the records, control rights, evidence access, and reporting path required by its jurisdiction. British and Maltese reporting duties remain with the responsible licensee even when a supplier raises the initial alert.
Does every sportsbook system or release need an independent laboratory certificate?+
No universal rule supports that claim. The required assurance depends on the jurisdiction, component, product, and change. Ontario requires specified games and critical systems to be certified by an AGCO-registered laboratory, while the UKGC applies its RTS and testing strategy to the relevant remote and software licensees. GLI-33 is a technical reference only where the regulator adopts or accepts it for the stated scope.
Are open bets always treated as protected customer funds?+
No. Legal classifications differ. The UKGC's specific framework excludes stakes committed to open bets from its definition of customer funds, while the MGA's player-funds reporting calculation includes open bets and pending withdrawals. Keep ledger components and liabilities separate and apply the exact local protection, accounting, and reporting rule.
What changes can affect a sports betting license after approval?+
Potential triggers include ownership or control, directors and key people, funding, licensed activities, channels, brands or domains, technical setup, suppliers, payment methods, policies, terms, and material outsourcing. The filing type and timing are jurisdiction-specific. Great Britain has a distinct corporate-control process, while Malta applies several approval and notification routes to people, systems, payments, and entity changes.
What must be planned before a sportsbook license is surrendered?+
For an active consumer-facing sportsbook, start with the local surrender process, then identify any applicable requirements for customer notices, registration and bet cutoffs, open and ante-post bets, funds, complaints, outstanding returns, records, supplier transition, and live-register status. A B2B supplier or another license state may have no player-facing steps. Great Britain's detailed closure steps are not a universal surrender procedure.
Sources
Primary documents and named publications used for the dated conclusions in this guide. Source links do not replace the requirements that apply to the exact entity, product, market, and contract.
Open 24 sources
- [1] Remote general betting standard real events licence
UK Gambling Commission · Checked
- [2] Betting: advice for remote, non-remote and betting intermediaries
UK Gambling Commission · Checked
- [3] What is gambling software?
UK Gambling Commission · Checked
- [4] What you need to send us when you apply for an operating licence
UK Gambling Commission · Checked
- [5] Personal Management Licence (PML) guide
UK Gambling Commission · Checked
- [6] Remote gambling and software technical standards (RTS)
UK Gambling Commission · Checked
- [7] Testing strategy for compliance with remote gambling and software technical standards
UK Gambling Commission · Checked
- [8] LCCP Condition 15.1.2: Reporting suspicion of offences etc – betting licences
UK Gambling Commission · Checked
- [9] Customer funds: assessing whether you hold customer funds
UK Gambling Commission · Checked
- [10] Notify the Commission of a change of corporate control
UK Gambling Commission · Checked
- [11] Closing a Gambling Commission licensed gambling business
UK Gambling Commission · Checked
- [12] Public Register
UK Gambling Commission · Checked
- [13] Remote Gaming Services
Malta Gaming Authority · Checked
- [14] Game Providers and Back Office
Malta Gaming Authority · Checked
- [15] Individual Requirements
Malta Gaming Authority · Checked
- [16] Anti-Money Laundering
Malta Gaming Authority · Checked
- [17] Player Protection
Malta Gaming Authority · Checked
- [18] Reporting Requirements
Malta Gaming Authority · Checked
- [19] 30-Day Notification Requirements
Malta Gaming Authority · Checked
- [20] Steps to Join the Ontario Market
iGaming Ontario · Checked
- [21] Sport and Event Betting Integrity
Alcohol and Gaming Commission of Ontario · Checked
- [22] Business to Consumer Licenses (B2C)
Gambling Regulatory Authority of Ireland · Checked
- [23] GLI-33: Standards for Event Wagering Systems, Version 1.1
Gaming Laboratories International · Checked
- [24] IBIA Data Standards
International Betting Integrity Association · Checked
This guide is a licensing and application framework, not legal, regulatory, financial, tax, technical-certification, integrity, AML, responsible-gambling, payment, or market-access advice. Sports betting rules change by jurisdiction, entity, customer location, equipment location, channel, product, event, supplier role, ownership, and production configuration. Verify the current law, regulator material, official register, license conditions, product and event approvals, testing scope, reporting duties, and closure process with the relevant authority and qualified local counsel before applying, launching, changing, or exiting.