How a casino game reaches players: studio to screen

When a player taps a slot in a casino app, at least four businesses are involved: the studio that made the game, often an aggregator that distributes it, the operator that runs the casino, and the platform that holds the player’s balance. This guide walks through that chain, because it explains much of what MediaSoftware reviews in its four sections.

Step 1: the studio builds the game

A studio designs the maths, the art and the client the player sees. The maths decides how wins are distributed; the client handles animation and sound; a game server settles each round with a random number generator. Studios usually ship a game in many languages and currencies at once.

Nocturn Play, for example, released thirteen new titles between 3 and 5 October 2026, from book-style and cluster slots to a 75-ball bingo, a naval battle game and a 3D coin pusher. Studios like this are covered in our studios section.

Step 2: the aggregator distributes it

Most studios do not connect to every casino themselves. They connect once to aggregators, which connect to hundreds of operators. The aggregator’s job is to:

• publish the game in a game feed with names, images, categories and supported currencies;
• return a launch URL when a player opens the game;
• route bet and win transactions between the studio and the operator;
• produce reports that both sides use for billing.

An operator can therefore add a new studio by switching it on in a back office, without a new integration. SoftAggregator, which lists more than 40,000 games from over 200 studios, is one of the aggregators reviewed, alongside its competitors, in MediaSoftware’s software section.

Step 3: the operator’s platform holds the wallet

The operator’s platform, sometimes called the PAM, holds the player account and balance. In the common seamless wallet model:

1. the player opens a game and the platform asks the aggregator for a launch URL tied to a session token;
2. the player bets; the game server sends a debit callback to the operator’s platform;
3. the round settles; a credit callback pays any win;
4. if something fails mid-round, a rollback reverses the debit.

Each callback carries a unique transaction ID so that a repeated message cannot debit or credit twice. When this part is built carelessly, players see wrong balances, which is why integration quality is a scored criterion in our methodology.

Step 4: the casino presents it to players

The casino decides where the game sits in the lobby, which currencies it is offered in and which promotions apply. Players see none of the chain above; they see a tile, a welcome offer and a cashier. That is why our casinos section scores what players actually touch: the games on offer, bonus and promo code, payments and crypto, the mobile app, support and withdrawals.

Where sport fits in

A sportsbook follows the same pattern with different content. Instead of a game server there is an odds feed and a betting engine; instead of rounds there are bets settled when events finish. Providers such as Nocturn Sport deliver pre-match and live markets, including esports, through an API that can share the casino’s wallet. These products are reviewed in our sportsbook section.

Why the chain matters for readers

• Operators comparing aggregators should test the steps above in a sandbox, not just compare catalogue sizes.
• Studios reach players faster through aggregators, but their games still have to load quickly on a phone in the player’s currency.
• Players benefit when every link works: games that open in their currency, balances that update instantly and withdrawals that are not held up by a failed callback.

---

MediaSoftware has commercial relationships with SoftAggregator, Nocturn Play and Nocturn Sport, which are used as examples on this page. See our editorial policy.

MediaSoftware editorial desk