Casino platform
The casino platform your operation actually runs on
Player accounts, one wallet, bonuses, payments, reporting and a back office your team can work in — with 150+ providers and 18,000+ games already connected. Launch from scratch, take a white label, or migrate a platform you have outgrown.
Definitions
What a casino platform is — and what it is not
A casino platform is the system that knows who your players are and what happens to their money. It opens and verifies accounts, holds the balance, applies bonuses, records every bet and settlement, moves deposits and withdrawals, and gives your team a back office to run all of it. Everything a player sees is a front end sitting on top of that.
Three things get called “the platform” and they are not the same. A casino game aggregator supplies games through one connection — it does not hold player balances. A game studio builds the games themselves and supplies nobody’s accounts. The platform is the layer underneath both: accounts, wallet, bonuses, compliance, reporting.
The distinction matters at the point you sign. An aggregator contract gets you content. A platform contract gets you a business you can operate. Most operators need both, and a lot of the friction in this industry comes from buying them from two suppliers who have never tested the seam between them.
IGP supplies both, plus sportsbook software and land-based integrations, on one back office. You can still take just the platform.
At a glance
- What it is: the player, wallet and back-office system behind an online casino
- Core parts: accounts and KYC, wallet and cashier, bonus engine, lobby and CMS, reporting, back office
- Content: aggregator built in — 150+ providers, 18,000+ games
- Verticals: casino, live casino, sportsbook, land-based — one balance
- Routes: build on it, white label it, or migrate onto it
- What it is not: a games catalogue, and not a licence
What is inside
Eight systems, one back office
These are the parts an operator actually uses every day. If a supplier cannot show you each of them working on a live account, the demo is a slide deck.
Player accounts
Registration, verification, document handling, limits, segments and the audit trail behind every change.
Wallet
One balance across casino, live casino and sport. Multi-currency, and crypto where the market allows it.
Cashier
Deposits and withdrawals through the rails that actually convert in your market, with routing and retries.
Bonus engine
Welcome offers, free spins, cashback, wagering rules and tournaments — configurable without a release.
Lobby & CMS
Game order, categories, banners, landing pages and copy, controlled by your team rather than a ticket.
Reporting
GGR, NGR, bonus cost, provider-level performance and player-level history, reconciled to one set of numbers.
Risk & compliance
KYC and AML workflows, responsible-gaming limits, self-exclusion and the reports regulators ask for.
CRM & affiliates
Campaign triggers, player messaging and affiliate tracking, or hooks into the tools you already run.
One balance
Casino and sportsbook on the same wallet
Most operators who run sport and casino as two products discover the same thing: the cross-sell never happens because the player has to move money between them. One wallet removes that step, and it also removes the reconciliation work nobody budgets for.
Seamless wallet
The balance stays in the platform. Every provider call checks and updates it in real time. One number, one statement, no sweep jobs — and the platform is the single source of truth if a session ends badly.
Transfer wallet
Funds move into a provider sub-account and back out. Simpler for a provider to certify, but the player sees transfers, and your finance team sees two places money can sit.
Both models exist for real reasons, and some markets and providers still force the second one. The comparison matters enough that it has its own write-up, and the same choice runs through the casino API.
Three routes
Build on it, white label it, or take it over
The right route depends on who holds the licence and how much of the operation you want to own. It is not a maturity ladder — established operators pick white label for a new market, and first-timers sometimes go straight to their own licence.
Platform only
You hold the licence and the player relationship. We supply the platform, the games and the integrations. You keep full control of brand, payments, bonuses and data — and full responsibility for compliance.
White label
You run brand, traffic and retention on a licence that is already live. Fastest route to a working casino, with less control over payments and terms. The trade-offs are set out on the white label casino page.
Turnkey
Platform, content, payments, design and launch support delivered as one project, on your licence. You end up owning the operation, without assembling six suppliers to get there.
A fuller comparison of the three, including who carries which risk, is in white label vs turnkey vs self-service.
Migration
Moving off a platform you have outgrown
Most platform conversations are not greenfield. They start because reporting cannot be trusted, a market needs a payment method the current supplier will not add, or the bonus engine needs a developer for every campaign. Migration is a project with a known shape.
Audit
What data exists, in what state, and what the current contract lets you take with you. This is where most surprises live.
Mapping
Accounts, balances, bonus liabilities, KYC status and history mapped field by field, then run against a copy.
Parallel run
Both systems reconcile against the same day before anything is switched. Numbers match or the date moves.
Cutover
A window, a rollback plan and a support rota. Players keep their balance, their history and their login.
The honest version: a migration is dominated by the quality of the data you are leaving, not by the platform you are moving to. Anyone who quotes a timeline before seeing an export is guessing.
Which piece you need
Platform, aggregator or API
Operators often ask for one of these and mean another. The difference is what each one is responsible for when something goes wrong.
| You need | Take this | Because |
|---|---|---|
| To launch a casino | Casino platform | You need accounts, wallet, bonuses and back office before games matter at all. |
| More games on a platform you already run | Game aggregator | One contract and one integration instead of a separate deal per studio. |
| To connect your own system | Casino API | Your developers want endpoints and a wallet model, not a product. |
| Slots only | Slots API | The slot catalogue without live studio certification and streaming overhead. |
| Live dealer only | Live casino API | Real tables and streams, which carry different market and latency constraints. |
| Sport alongside casino | Sportsbook software | One wallet across both, rather than two products and two balances. |
| Dual-currency play | Sweepstakes aggregator | Gold-coin and sweeps-coin models need games certified for that mode. |
| Halls and online together | Land-based integrations | One player account and one set of numbers across terminal and web. |
Markets
The platform is the same; the market is not
Provider availability, payment rails, certification and reporting duties change at every border. A platform that ignores that is a platform you will be patching in six months. We confirm what can actually go live in your jurisdiction before anything is signed.
Scale
A scalable casino platform fails at the edges, not the middle
Operators ask about concurrent players. In practice the platform core is rarely what gives way first. What gives way is the slowest thing in the chain on the busiest night: one game studio timing out, a payment provider queueing withdrawals, a lobby loading every thumbnail before it paints, a report query running against live data at peak.
So the questions worth asking are narrower than “how many users”. Does a failing provider degrade to a hidden category, or to an error in front of the player? Are reports served from a read copy, or from the table the wallet is writing to? Does the lobby paginate, or does it ship eighteen thousand tiles? Is there a cache in front of the catalogue, and how stale can it get before a player clicks a game that is switched off?
Traffic peaks in this business are predictable: a tournament final, a payday, a campaign that lands. Capacity is the easy half. The hard half is what the product does while one dependency is slow, and that is a design decision, not a server size.
What to test before signing
- Kill one provider in a sandbox and watch the lobby
- Run a report during a load test and check wallet latency
- Queue a withdrawal batch and watch the cashier
- Open the lobby on a throttled mobile connection
- Ask what the catalogue cache TTL is
- Ask what happened during their last incident
Payments
Payments decide whether a market works
A casino platform can be flawless and still fail in a market because players cannot deposit the way they expect to. This is the part of a platform project that takes the longest and gets scoped the shortest.
The method people actually use
Interac in Canada, e-wallets and bank transfer across Asia, mobile money in parts of Africa. Cards alone convert badly almost everywhere outside a handful of markets.
Your merchant account, your timeline
Payment providers underwrite the operator, not the platform. Integration is days; approval can be weeks, and it is the item that usually moves a launch date.
More than one provider per method
Single-provider setups fail closed. Routing, retries and a fallback per method keep deposits converting when one processor has a bad hour.
What is live in each jurisdiction is set out on the markets pages, and confirmed for your specific licence before a launch date is agreed.
Due diligence
Ten questions that separate platform suppliers
Ask these in the demo, not after the contract. The answers are short if the product is real.
- Whose licence? Platform on your licence, or a white label on theirs — and what changes if you switch later.
- Seamless or transfer wallet? And which providers force the other model.
- Who owns the player data? Written into the contract, including what you can export and in what format.
- Can your team launch a bonus alone? Without a developer and without a release window.
- Which payment methods are live in my market? Live today, not on a roadmap.
- How do provider outages surface? Whether the lobby hides a broken studio or shows an error to the player.
- Do the reports reconcile? Platform, aggregator and payment figures agreeing on the same day.
- What is the exit? Notice period, data export and what happens to balances.
- Who answers at 2am? A named contact and a rota, or a ticket form.
- What is not included? The list a supplier gives here tells you more than the feature grid.
FAQ
Casino platform — common questions
The system that runs an online casino behind the scenes: player accounts and verification, the wallet that holds balances, the bonus engine, the cashier, reporting, and the back office your team works in. Games sit on top of it and come from a game aggregator. The platform is what makes the operation a business rather than a games page.
An aggregator supplies content through one connection and never holds a player balance. A platform holds the accounts, the money and the compliance record. You need both to operate; the mistake is assuming an aggregator contract gives you a casino.
For the platform on your own terms, yes — the licence is yours and so is the player relationship. If you do not hold one yet, a white label lets you operate under a licence that is already live, with less control over payments and terms. IGP supplies software; it does not issue licences.
The aggregator is built in: 150+ providers and 18,000+ games through one integration. Which of them you can actually switch on depends on your jurisdiction and certification, so the usable catalogue is confirmed market by market rather than promised in full.
Yes, and it is a common reason operators call. The work is audit, field mapping, a parallel run that reconciles both systems on the same day, then a cutover window with a rollback plan. Players keep balances, history and logins. Timelines depend on the quality of the data you are leaving, which is why nobody should quote one before seeing an export.
Yes. Sportsbook runs on the same wallet and the same back office, so a player moves between sport and casino without transferring funds and your reporting covers both. It can also be taken separately.
Seamless by default: the balance stays in the platform and every provider call checks it in real time, which keeps one source of truth. Some providers and some markets still require a transfer model, and that is handled per integration rather than forced on the whole setup.
The software side is the short part. What sets the date is your licence status, the payment providers you need approved in that market, and the certification each game studio requires there. We give a date after those three are known, not before.
Further reading
Before you decide
How to score a shortlist, what a migration involves and the order a launch actually happens in are covered in the operator guides. Regulatory changes and market data as they land are in industry news.
Tell us what you are launching
Your market, your licence status and what you already run. That is enough for a straight answer on what the platform can do for you and how long it takes.
