Glossary
What is a game aggregator?
A game aggregator is a company that connects online casino operators to many game studios through one integration, one contract and one wallet, so the operator does not have to integrate each studio separately.
3 min readUpdated By the Turnkeyxgaming team
What is a casino game aggregator, in more detail?
A casino game aggregator maintains a technical connection to each studio's remote gaming server and exposes all of them through a single API. It translates launch and wallet calls, tracks which games are certified in which markets and produces one reconciliation report across studios. It is usually paid a share of GGR on the games it supplies.
It is not a studio (it does not make games), not a platform (it does not run player accounts) and not a payment provider. Some companies offer all of these, but they are separate products.
What to test before you call the catalogue one integration
Ask for a launch, a debit, a credit and a void against two studios that do not share a protocol. If both rounds land on one wallet contract and one reconciliation file, you are looking at aggregation. If the second studio needs its own adapter, its own error codes or its own invoice layout, you are looking at a reseller who still left the integration work with you.
Then ask which titles disappear in each market you hold a licence for. A single game count that does not change by country is a sales total. The operational list is the one filtered by certification. Keep that filtered list in writing per brand. The how an aggregator works guide is the machinery. This entry is the boundary of the word.
Jobs that sit next to aggregation and are not it
| Job | Who owns it | What aggregation does not replace |
|---|---|---|
| Making the game and its maths | The studio | A translated protocol is not a new game |
| Player account, KYC, limits, cashier | The operator platform | One wallet contract assumes the account already exists |
| Which titles a licence may offer | The operator, from certification records | A global count is not a market list |
| Monthly matching of stake and win | Finance, against one file | The file does not choose your bonus rules |
| Taking payment from the player | Your PSP | Game traffic is not a deposit |
One contract is not one product
Companies sell aggregation beside a platform or a turnkey build. Ask which contract launches games, which contract holds the player, and which invoice is the GGR share. If the answer is a single brand name, you do not yet know what you are buying.
One trading day across four studios, on one file
Take a Saturday in a market where the content rate is 13% of GGR. Four studios are live on the brand. Studio A settles €18,400 of stakes and €16,900 of winnings. Studio B settles €6,200 and €6,450. Studio C settles €27,000 and €24,300. Studio D is offline all day and settles nothing.
Total stakes are €51,600 and total winnings €47,650, so the day's GGR is €3,950. At 13% the content fee for that day is €513.50. That is one sum for four studios, which is the commercial point of aggregation and also the least interesting part of it.
The per-studio rows matter more than the total. Studio B ran at minus €250, which is a real result and not a data error, and it is the row a spreadsheet sorting by revenue will place last or delete. Studio D's zero is not a missing file, it is a studio with no rounds, and the empty row has to survive into the reconciliation or nobody notices its games were dark for a day.
One file does not by itself mean one net position. Whether Studio B's negative day is netted against the other studios, carried forward, or billed separately is a commercial term in your agreement, and some studio contracts require a minimum regardless of a negative result. Read that clause before finance assumes the total is the invoice. A large operator with its own integration team may also negotiate consolidated terms directly with studios; aggregation is the cheaper route for most brands, not a universal law. The saving here is not only the fee. It is the one page, with the netting rule written beside it.
What operators get wrong when they count the catalogue
- Adding studio counts from four different sales decks and calling the sum a catalogue. Ask for the game record with ids, not the slide.
- Assuming a title is launchable in a market because the studio says it is certified somewhere. The filtered list per brand is the one that decides.
- Expecting an automatic credit for a studio outage. The fee follows settled GGR, which already falls; anything beyond that is a contract term, so agree it before launch rather than after an outage.
- Letting the lobby filter be the only place a market's restricted titles are removed, so a favourite link still launches what the list no longer offers.
- Keeping reconciliation inside the supplier relationship. Finance has to be able to run the file without asking account management for permission or for a password.
FAQ
Questions operators ask
Is Turnkeyxgaming a game aggregator?
Yes. The casino API aggregator page is that product: studio connections, one contract and one reconciliation file. Which studios a licence can switch on is confirmed in writing, not by this definition.
Does the aggregator set the RTP of a studio's game?
No. The studio certifies the build. Aggregation records which build you enabled and settles the round the game reports. It does not retune the maths.
If we leave, do we keep the studio connections?
You keep whatever your exit terms say you can export, which should be agreed before launch. The studio protocols themselves stay with the aggregator that built them, unless you have also signed those studios directly.
If we add a studio after launch, does our wallet work change?
Not if the integration is genuinely aggregated. The new studio's games call the same debit, credit and rollback contract, so the work is configuration and certification rather than a new adapter. Ask for a launch test on the new studio against your existing sandbox wallet before you accept the change, and get the market list for its titles in writing.
Who fixes a game that pays the wrong amount?
The studio, on the certified build. We can reproduce the round, produce the callback log and confirm what the wallet was asked to pay, and that evidence usually closes the ticket. Retuning a paytable is not something aggregation can do, and no lab report would survive it.
References
Sources and further reading
Primary regulator, standards or studio documentation behind the technical and regulatory points on this page. External links open in a new tab. Links checked 2026-11-15.
- Malta Gaming Authority
Licensing and player-protection rules for Malta-licensed operators.
www.mga.org.mt
- eCOGRA
Independent testing and RNG certification for online gambling software.
ecogra.org
Keep reading
Related pages
- Product · Game aggregationAggregatorOne aggregator contract for licensed operators: 40,000+ games from 300+ studios at 13% of GGR in Asia and 16% elsewhere.Read
- Guide · AggregationHow aggregators workAn aggregator turns many studio protocols into one wallet contract and one reconciliation file, so your team builds four endpoints once.Read
- Guide · DefinitionsCasino API vs aggregatorA casino API is the interface; an aggregator is the business that puts many studios behind one of those interfaces. Know which you buy.Read
- GlossarySeamless walletA seamless wallet keeps the balance on the operator's ledger and posts every bet and win as a live callback, per round, in the session currency.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.