An iGaming platform is the software layer that connects player accounts, money records, gambling products and operator controls for an online casino or sportsbook. It may include a player account management system, wallet, back office and integrations with games, payments, identity services, risk tools and regulatory reporting.
This article is for industry researchers, operators, investors, journalists and buyers comparing platform claims. It maps the common components and licensing boundaries. It does not rank vendors, estimate launch costs or claim that every platform contains the same modules.
What does an iGaming platform do?
The platform coordinates the records and workflows needed to run remote gambling. A customer registers, completes required checks, funds an account, opens a game or betting market and receives a settled result. The platform either performs each step or passes data to a connected service and records the response.
The term is commercial rather than a single universal regulatory category. One vendor may sell a broad platform with casino, sportsbook and managed services. Another may supply only the player account and wallet layer. A third may call a game aggregation gateway a platform. The component map and contract matter more than the product label.
Regulatory sources describe the parts more precisely. The Gambling Commission's gambling software guidance includes gambling-specific software for bet capture or matching, settlement, random number generation and detailed gambling records. It excludes general business applications that are also used outside gambling.
The main iGaming platform components
| Role | What it means | Where to verify |
|---|---|---|
| Player account management | Creates and controls customer identities, account status, sessions, limits and account history. | Account model, identity workflow, status controls, audit trail and jurisdiction configuration. |
| Wallet and ledger | Records deposits, withdrawals, wagers, wins, bonuses, adjustments and balances. | Ledger design, reconciliation process, currency handling, transaction IDs and correction controls. |
| Casino and game layer | Launches games and connects studios, aggregators, remote game servers or live casino services. | Provider contracts, game IDs, certification scope, launch flow and result records. |
| Sportsbook layer | Handles event data, markets, odds, bet capture, risk decisions, settlement and result corrections. | Trading model, data rights, bet lifecycle, liability controls and settlement rules. |
| Payments and identity | Connects payment providers, KYC, age verification, AML screening and fraud tools. | Supplier list, data flow, fallback process, market coverage and responsibility matrix. |
| Bonuses and CRM | Configures promotions, eligibility, communication and customer segmentation. | Terms logic, wagering records, approval rights, exclusion controls and change history. |
| Back office and reporting | Gives authorised staff operational controls, reports, audit logs and regulatory data exports. | Role permissions, immutable logs, report definitions, retention and regulator access requirements. |
The table is a functional map, not a claim that one supplier owns every component. Many production stacks combine several vendors. The operator still needs to know which system is authoritative for the player account, cash balance, bet record, self-exclusion state and regulatory report.
How a player transaction moves through the stack
A typical transaction crosses several services. Following the sequence exposes missing controls and unclear ownership more effectively than a feature list.
- The player account system creates or retrieves the customer record.
- Identity, age, location or risk checks return a decision to the operator workflow.
- The payment service processes a deposit while the wallet records the resulting movement.
- The platform creates an authenticated session with the selected game or sportsbook service.
- The gambling system records the wager and the product service determines or receives the result.
- Settlement updates the player ledger and stores the transaction history.
- Back-office reports and audit logs preserve the events needed for operations and regulation.
Every handoff needs an identifier, timestamp and ownership rule. If the payment provider reports success but the wallet does not update, the reconciliation process must resolve the difference. If a game result arrives twice, settlement controls must prevent a duplicate balance change. These are platform questions even when an outside supplier caused the event.
Player account management and wallet
Player account management, often shortened to PAM, is the record layer for the customer relationship. It holds identity and account status, connects sessions to one player and enforces configured controls. The wallet and ledger record the financial consequences of deposits, withdrawals, stakes, wins, bonuses and manual adjustments.
The GLI-19 Interactive Gaming Systems standard includes player account registration and verification, financial transaction records, game history, incentive records and reporting requirements. It also notes that interactive gaming systems can be modular and that the production configuration selected by the operator matters to testing.
A single-wallet product keeps a common balance across products. A multi-wallet design separates balances or bonus logic by product, market or currency. Neither architecture is automatically better. The due-diligence question is how balances reconcile, which ledger is authoritative and what happens when an integrated service is unavailable.
Games, aggregation and remote game servers
A casino lobby is a catalogue and navigation layer. The games can come from many studios through direct integrations or a game aggregator. The aggregator reduces the number of commercial and technical connections, but it does not necessarily develop the games or determine every result.
A remote game server, commonly shortened to RGS, hosts game logic and records or determines outcomes for the games it serves. A platform can integrate several RGS providers through one aggregator. Researchers should therefore record the platform, aggregator and game studio separately rather than assigning the whole casino stack to the brand shown in the lobby.
Certification also follows the configured product and jurisdiction. A report for one game version, random number generator or integration does not prove that every later configuration is covered. The production game ID and version should match the test or approval evidence relied on by the operator.
Sportsbook technology is its own operating chain
A sportsbook combines event and results data, market creation, odds, bet acceptance, risk management, settlement and player-facing presentation. The operator may run its own trading team, outsource trading and risk, or use a managed sportsbook. The platform contract should identify who can suspend a market, change a price, void a bet and correct a result.
Sportsbook and casino can share a PAM and wallet while using separate gambling engines. That separation matters in incident analysis. A login or balance failure may sit in the common platform, while a disputed game result or market settlement can originate in the product-specific system.
The Gambling Commission lists bet capture or matching and settlement among the software functions that can constitute gambling software. Its guidance also makes clear that a gambling software licence alone does not authorise a company to provide gambling facilities to customers.
Compliance is a system property
Compliance tools are often sold as integrations, but the regulated outcome depends on the complete system and operating process. Identity checks, limits, game rules, transaction display, result determination, interrupted gambling and security controls cross several platform components.
The Gambling Commission remote technical standards cover customer account information, transaction display, game descriptions, result determination, random outcomes, interrupted gambling, financial limits, responsible product design, in-play betting and third-party software. The standards were last updated on 20 March 2026 when this article was researched.
A vendor certification, module test or licence can support compliance evidence, but the operator still needs assurance for its production configuration. GLI-19 likewise states that integrated systems may contain configurable features and that the configuration used in production should be communicated for a functionally equivalent test environment.
Platform supplier and operator are different roles
The platform supplier provides technology. The operator provides the gambling facilities and holds the customer-facing responsibility where the applicable law requires it. One group can perform both roles, but the authorisations should still be checked separately.
In Great Britain, the Gambling Commission says a gambling software licence authorises manufacture, supply, installation and adaptation of gambling software. It does not permit the provision of gambling facilities. A business that also provides those facilities needs the relevant remote operating licence. The Commission's software licence guidance further explains how the required permission follows the activity performed in the supply chain.
Malta uses a separate B2B critical gaming supply framework. The MGA Game Providers and Back Office page includes software that generates, captures, controls or processes essential regulatory records, along with the control system on which that software resides. The same framework separately licenses B2C gaming services.
Our gambling licence explainer shows how to separate holder, activity, market, channel and status. The operator and brand explainer covers the customer-facing legal entity.
Platform, white label, aggregator and frontend
| Role | What it means | Where to verify |
|---|---|---|
| iGaming platform | The connected operational software for accounts, money records, products and back-office control. | Module map, system of record, integrations, production configuration and supplier responsibilities. |
| White-label service | A broader operating arrangement in which a licensed service appears under a third party's brand. | Licensed operator, brand partner, customer contract, domain and allocation of regulated tasks. |
| Game aggregator | A gateway that connects an operator or platform to games from multiple suppliers. | Connected studios, commercial rights, game versions, certification chain and outage responsibility. |
| Frontend | The website or app interface through which customers browse products and manage their account. | Ownership, hosting, content controls, authentication boundary and APIs used to reach the platform. |
A white-label package can contain a platform, licence relationship, payments, managed operations and a configurable frontend. A platform sale can contain none of those additional services. The white-label gambling explainer describes the commercial and regulatory relationship behind that model.
How to assess a platform claim
A buyer or researcher should ask for a system boundary before comparing feature lists. The boundary shows what the vendor owns, what it resells, which third parties process regulated events and which system keeps the authoritative record.
- List every module included in the contracted product and identify its legal supplier.
- Map the player, payment, wager, result and reporting data flows.
- Name the system of record for identity, account status, cash balance and each product transaction.
- Match software and supplier authorisations to each target jurisdiction.
- Check the tested or certified version against the planned production configuration.
- Document incident, reconciliation, change-control and exit procedures.
- Separate the platform fee from third-party games, payments, data, hosting and managed services.
The result should be a responsibility matrix, not a one-line claim that the platform is fully compliant or turnkey. Compliance depends on the operator, suppliers, configuration and market. Commercial readiness also depends on contracts, data portability and the ability to replace an integration without losing authoritative records.
Frequently asked questions
Is an iGaming platform the same as an online casino?
No. The online casino is the customer-facing gambling service. The iGaming platform is part of the technology used to run it. The operator, brand, platform supplier, game aggregator and game studios can all be different companies, although one group may perform several of those roles.
What is a PAM in iGaming?
PAM means player account management. It creates and controls customer accounts, connects sessions to an identity and stores account status and history. It usually works closely with the wallet, compliance services and product integrations. The exact division between PAM and other modules varies by platform design.
Does an iGaming platform include games?
It can include game integrations or an aggregation layer, but the games may be supplied and hosted by separate studios or remote game server providers. Confirm which titles, versions and jurisdictions are contracted and approved. A large catalogue claim does not show who supplies or certifies each game.
Does a platform provider need a gambling licence?
It depends on the supplier's activities and the jurisdiction. Great Britain licenses specified manufacture, supply, installation and adaptation of gambling software. Malta licenses certain critical gaming supplies on a B2B basis. Providing gambling facilities to customers can require an additional consumer-facing operating authorisation.
What should be checked before choosing an iGaming platform?
Check the module boundary, system of record, supplier licences, target-market support, production certification, payment and game integrations, data ownership, reconciliation, security controls and exit process. Test a full player and transaction lifecycle. A feature list alone does not reveal where responsibility or operational risk sits.
The platform research rule
An iGaming platform connects player accounts, money records, gambling products and operational controls. Evaluate the actual modules, data flows, suppliers and production configuration. Then match each regulated activity to the operator or supplier authorisation required in the target market.
BETTIMES records companies, licences and commercial relationships separately in its company directory, licence directory and source-linked explainers. The BETTIMES source policy describes the evidence standard used for those records.
Why this record matters
BETTIMES links this publication to structured company, market and source records. Material changes can therefore be checked and refreshed without detaching the article from its original evidence.