The iGaming value chain is not a single line of companies. A player-facing operator assembles licensed gambling products from game or odds suppliers, hosts, aggregators, account and wallet systems, payment services and risk controls. Each layer can be in-house or contracted, and the legal boundary does not always follow the technical boundary. The useful map shows who supplies, who controls, who contracts with players and who is accountable in each market.
This framework is for investors, operators, suppliers and journalists trying to read the business behind an online casino or sportsbook. It is a functional model, not a ranking of vendors or a claim that every business has seven separate companies.
The seven functional layers
| Layer | Typical output | Question to verify |
|---|---|---|
| 1. Product creation | Casino game, RNG and maths model; sports event data or trading model | Who develops, versions and tests the product? |
| 2. Hosting and distribution | Remote game server, content aggregator, odds feed or managed trading service | Who runs the live service and controls the release? |
| 3. Account platform | Registration, identity state, limits, balances and transaction history | Which system is the authoritative player record? |
| 4. Money movement | Deposit, withdrawal, settlement and reconciliation | Who is merchant, PSP client and holder of player funds? |
| 5. Regulated operation | Market permission, terms, player protection and reporting | Which entity offers the gambling service to the player? |
| 6. Acquisition and service | Advertising, affiliates, CRM, support and complaints | Who approves claims, handles complaints and can intervene? |
| 7. Oversight and evidence | Testing, audits, regulator returns and source records | Can a third party reconstruct what happened and who decided? |
The order is conceptual. In a real session, several layers exchange data at once, and one firm may operate more than one layer. Do not infer a separate licence or legal entity from each row.
Product creation: games are not the same as casinos
A game studio can design a slot's rules, maths, assets and software, but the player encounters that game through a regulated operator's product. In Great Britain, the Gambling Commission's software guidance covers software involved in accepting and recording gambling transactions, determining results and allocating winnings. A gambling software permission does not alone allow the supplier to provide gambling facilities to consumers.
Testing is another layer, not a magic transfer of responsibility. The Commission's remote technical standards and the BETTIMES game-testing guide distinguish a product's tested configuration from the operator and supplier permissions needed to deploy it. For casino content, record the game title, version, RNG or game-engine boundaries, testing evidence, host and live operator.
Sportsbooks have a parallel distinction. Event data, an odds feed, trading tools and managed trading can be bought separately or bundled. The BETTIMES odds-feed comparison explains why a price feed is not the same as deciding which bets to accept or bearing trading risk.
Hosting and distribution: the invisible middle
The remote game server (RGS) hosts or manages a game's live logic and integrations. An aggregator connects multiple game suppliers to an operator through a distribution and integration layer. A supplier can do both, but those functions should not be conflated. See the RGS explainer and aggregator comparison.
Great Britain's casino game-host guidance describes a distinct case: a software business hosts games that players access through another operator, without contracting with those players itself. Malta's critical-gaming-supply rules similarly show that material game elements and essential regulatory-record systems may be regulated B2B supply. These are different regimes, but both show why the hosting layer should be named.
Account platform: one balance, several ledgers
A Player Account Management system (PAM) connects identity, account status, limits, sessions, bonuses, wallet and reporting. That does not mean it is the only authoritative ledger. A payment processor records a card or transfer transaction; an operator wallet records account balance; a game or sportsbook records a round or settled wager. Reconciliation links them.
The British RTS 1 customer-account standard requires accessible balance and gambling/account history for covered products. It specifically discusses deposits, withdrawals, bets, results, winnings and movement between products. That standard illustrates why an attractive front-end balance is not sufficient evidence that the full transaction trail is reconstructable. BETTIMES maps this layer in its PAM guide.
Payments and player funds: follow the money, not the logo
The cashier may display the operator's brand while payment acceptance, acquiring, wallets, settlement accounts and withdrawal approval involve several entities. The merchant of record is not determined by the banner or game supplier. Map a deposit and withdrawal separately, including failed transactions, reversals, chargebacks, currency conversion and balance reconciliation.
In Great Britain, the Gambling Commission's customer-funds guidance says its segregation condition applies to most remote operators holding customer funds, but not to the listed B2B activities. The rule demonstrates a responsibility boundary; it does not describe every country's safeguarding model. The BETTIMES MCC 7995 guide explains why merchant coding, licensing and payment bans must also be analysed separately.
Operator and market access: the contract that matters to players
The operator is the legal entity offering the gambling service within a market's authorisation framework. It may also own the brand, but a brand can be a separate commercial partner. Great Britain's third-party guidance says compliance responsibility for operating gambling websites, including white-label sites, sits with the licence holder. The regulator expects due diligence, oversight and controls when the licensee relies on contractors.
The market gate changes across borders. Malta distinguishes a B2C Gaming Service Licence from defined B2B Critical Gaming Supply. iGaming Ontario's entry steps require an operator to work with iGO and the AGCO, while some suppliers need separate registration and technology certification. Neither market's approvals should be projected onto another. The BETTIMES operator/supplier licence guide provides the legal map.
Acquisition, retention and oversight are not afterthoughts
SEO, paid search, affiliates, sponsorships and CRM bring players to the product, but the marketing channel does not determine who is licensed. A third-party agency can acquire traffic without becoming the operator; the operator still needs a documented approval and oversight process where applicable. The BETTIMES traffic-source guide separates acquisition mechanisms from partner relationships.
Customer support, responsible-gambling interventions, AML reviews, disputes and regulator reporting often depend on data from multiple systems. A provider may generate an alert, while a licensee or designated function decides and records what action to take. The Commission's third-party guidance is a useful example: outsourcing a task does not by itself outsource the licensee's compliance accountability.
Due-diligence worksheet: turn the diagram into evidence
For each layer, collect five fields: legal entity, product or function, market permission, decision owner and source record with verification date. Then run one player journey from registration to withdrawal. At every hand-off, ask which system creates the record, which system is authoritative, which party can change it and who can export it if the supplier relationship ends.
| Event | Minimum trace |
|---|---|
| Registration | Legal contracting entity, identity decision and account creation record |
| Deposit | Instrument, PSP/acquirer, merchant, settlement account and wallet posting |
| Game round or bet | Supplier, host, game/bet ID, stake, result, settlement and version |
| Player-risk alert | Trigger, evidence, human or automated decision owner and outcome |
| Withdrawal | Approval, wallet debit, PSP/bank payment and reconciliation |
| Complaint or regulator query | Case owner, supporting event history and retention route |
If the platform vendor cannot produce a sample trace across these events, the diagram is still a sales diagram, not an operating model. Do not fill missing cells with assumptions.
Frequently asked questions
Is an iGaming platform the same as an operator?
No. A platform can supply the account, wallet, game integrations and reporting tools, while another legal entity contracts with players and holds the consumer-facing authorisation. Some groups perform both roles, and contracts may bundle managed services. Verify the exact legal entity, licensed activity and regulated decision owner for the target market.
Where does a casino game aggregator sit?
An aggregator usually sits between game suppliers or hosts and the operator's platform. It can simplify content integration and distribution, but it does not automatically create game mathematics, hold player funds or operate the consumer casino. The exact function depends on its contracts, architecture and any supplier permissions required by the market.
Who owns the player data in the value chain?
There is no single answer from a diagram. Separate the legal controller or processor role for each purpose from database access, contract rights and technical export capability. Account, game, payment and marketing records may be held in different systems. Ask for a data map and test a documented export before signing a platform deal.
Can the operator outsource compliance?
An operator can contract for technology and services, but that does not necessarily transfer its regulatory accountability. Great Britain's Gambling Commission expressly requires oversight of third parties acting in licensed activities and says responsibility for white-labelled operating websites remains with the licence holder. The permissible outsourcing model and controls must be checked market by market.
Is there one standard iGaming value chain worldwide?
No. Product types, legal categories, market-entry agreements, payments infrastructure and reporting duties vary. The seven-layer map is a functional checklist, not a legal taxonomy. Use it to identify the actual companies and evidence in one product and territory, then repeat the exercise before entering another market.
Source and review note
Primary sources reviewed on 23 September 2026: UK Gambling Commission software guidance, game-host guidance, RTS 1, customer-funds and third-party guidance; Malta Gaming Authority B2C and critical B2B supply descriptions; iGaming Ontario market-entry steps. The diagram is BETTIMES editorial synthesis, not a regulator-published value-chain model.
Editorial conclusion: follow the player transaction across product, account, money and decision records. That reveals more about an iGaming business than a vendor list or a diagram made of logos.