Casino software aggregator: what a casino aggregator is and how it works

What is a casino aggregator?

A casino aggregator is a wholesale distributor of casino games. It holds the commercial and technical relationships with many game studios and exposes all of their titles to operators through one integration. Instead of negotiating, certifying and coding a connection to each studio, the operator connects once and switches games on from a single catalogue. The aggregator collects its fee, usually a share of gross gaming revenue, and pays the studios from it.

The model exists because studio-by-studio integration does not scale. Each studio has its own launch flow, its own transaction format and its own invoice. A brand that wants a few hundred slots, a live casino and some crash games would otherwise be maintaining dozens of separate connections. An aggregator turns that into one.

How a casino software aggregator works, step by step

The mechanics are similar across vendors, even if the method names differ.

1. Catalogue request. The operator's platform calls the aggregator for the list of games available to its account, with identifiers, categories and thumbnails, and builds the lobby from it.
2. Player registration. The platform tells the aggregator which player is about to play and in which currency.
3. Game launch. The aggregator returns a launch URL, which the operator displays in an iframe or a new window.
4. Wallet callbacks. During play, the aggregator calls the operator for every balance check, bet and win. In a seamless wallet the money never leaves the operator's system; the operator approves or refuses each debit in real time.
5. Reporting and billing. GGR is calculated per game and per studio, and the aggregator invoices or deducts its share.

SoftAggregator's public documentation shows the minimal version of this flow: three calls (game list, player creation, game launch) reach a first round, after which the operator only answers balance, debit and credit callbacks. Reading a specification at that level of detail is the quickest way to understand what any aggregator expects from a platform.

Seamless wallet or transfer wallet

A seamless wallet keeps one balance on the operator side and lets the aggregator query it per transaction. A transfer wallet moves money into a separate balance held for the game session and back out afterwards. Seamless is now the default for most operators because players see one balance across slots, live tables and betting, and reconciliation stays in one place. Hub88 publishes support for both options; SoftAggregator and AggregatorCasino run seamless wallets, and so does the sportsbook each of them carries, which is why a bet on a football match and a spin on a slot draw on the same balance.

Aggregator or direct studio contracts?

Direct deals can make sense for a very large operator that concentrates most of its traffic on a handful of studios and has the engineering capacity to maintain several integrations. For almost everyone else, an aggregator is cheaper in total once integration time, certification and invoice reconciliation are counted. Some operators run a hybrid: an aggregator for breadth and one or two direct contracts for their highest-volume studios. Before going direct, it is worth checking whether the saving on revenue share outweighs the cost of the extra integrations.

What separates one casino aggregator from another

Catalogue counts dominate marketing, yet past a certain size they converge because aggregators license from overlapping pools of studios. The differences that change an operator's costs sit elsewhere.

• Price transparency. SoftAggregator prints a rate per vertical: slots at 9% of GGR, live dealer at 11%, betting at 12%. AggregatorCasino publishes rates from 9%. The other vendors in the main ranking quote privately.
• Entry cost. Setup, integration and monthly fees range from zero to significant. Both of the top two charge nothing to connect.
• Verticals on one wallet. Casino-only aggregators leave betting to a second supplier. A sportsbook on the same wallet saves that work later.
• Documentation access. Public specifications let an engineer review idempotency, retry handling and rollback behaviour before committing.
• Currencies. SoftAggregator supports 38 ISO currencies across its broadest slot range and its betting product; NuxGame publishes 180+ at platform level. Coverage differs by studio, so the useful check is the catalogue filtered by the currencies a brand will actually use.
• Compliance footprint. SOFTSWISS publishes 25 pre-certified jurisdictions and SoftGamings a long licence list. That counts only if it covers the markets on the operator's roadmap.

Where each reviewed aggregator fits

SoftAggregator and AggregatorCasino suit operators that run their own platform and want content and betting quickly at a known price. Hub88 fits API-first casino operators that value back-office tooling. SOFTSWISS and EveryMatrix fit larger operators with regulated-market plans and procurement processes. Slotegrator, SoftGamings and NuxGame package aggregation with platform services for teams that want fewer suppliers. The SoftAggregator vs SoftSwiss comparison shows the self-service and enterprise models side by side.

A short checklist for a first aggregator

• Request the game list filtered by target countries and currencies.
• Read the wallet specification, especially duplicate callbacks and rollbacks.
• Get the rate for each vertical in writing, plus any fees outside revenue share. The free casino API guide lists what to ask.
• Ask how long a first live game takes after keys are issued; see the quick casino API guide.
• Confirm how game identifiers and round history can be exported if the operator ever leaves.