Turnkeyxgaming

Guide · Aggregation

How does a game aggregator work?

An aggregator turns hundreds of studio integrations into one. This guide explains what happens behind that single API: studio connections, translation, certification, reconciliation and the commercial model that pays for it.

8 min readUpdated By the Turnkeyxgaming team

The problem aggregators solve

Each studio publishes its own integration: its own launch format, wallet protocol, error codes, currency handling and certification pack. An operator that wants fifty studios directly faces fifty integrations, fifty wallet adapters and fifty monthly invoices in fifty formats. Each studio's updates then become the operator's maintenance work.

An aggregator does that work once, for every operator. It builds and maintains each studio connection and exposes a single contract upward. The operator integrates once and gains every studio the aggregator carries, subject to licences.

The four layers inside an aggregator

  • Studio adapters

    One connector per studio, translating launch, wallet and reporting calls to and from that studio's protocol.

  • Normalisation

    Game IDs, categories, currencies and error codes mapped into one consistent model for operators.

  • Wallet proxy

    Studio wallet calls forwarded to the operator's seamless wallet, with retries and idempotency enforced.

  • Reconciliation

    Every round logged so GGR per studio, game and brand can be matched against studio invoices.

Certification and market control

In regulated markets, studios and often individual games must be approved. An aggregator keeps a per-market record of which studios and titles are certified, and filters each operator's catalogue accordingly. This is a large part of the value: an operator with licences in three countries gets three different catalogues without managing the certification records itself.

How aggregators are paid

Aggregators usually charge a share of GGR, meaning stakes minus wins on their games. Studios charge the aggregator their own rate, and the aggregator's margin sits between the two. Some quotes show one all-in rate. Others list studio rates and add a margin. The pricing page is where the published rates and the other fee lines are set out. Read it before you treat a headline percentage as the whole contract.

What an aggregator does not do

An aggregator does not license you, run your KYC, process payments or design your lobby. It does not change a studio's game maths or certified RTP. If a supplier claims to do all of those inside the aggregation fee, ask exactly what is included. Some of them belong to a platform or turnkey contract, as the glossary entry on game aggregators explains.

The night a studio stopped sending zero-win callbacks

One slot studio's adapter went through a routine release on a Tuesday morning. That night, rounds that ended with no win stopped producing a credit callback. The client still animated the loss and the player saw the stake gone, so nothing looked wrong on the front end. At 09:00 the studio's own cleanup job treated every unclosed round as unfinished and returned the stakes: 214 rounds, €1,860.

The overnight report showed 214 open rounds against a studio claiming none. It was caught because round count per studio is compared with closed-round count and the gap was too large to be lag. By 09:40 the studio's void list was in hand; by 11:15 every returned stake was matched to a round whose win had genuinely been zero. Players had been paid back for bets they lost. The €1,860 ended as a goodwill decision rather than a technical recovery, and the month's invoice carried it until a credit note arrived.

The lesson is not about that studio. A round closes on the credit callback, including a zero, and an adapter that suppresses empty wins to save a request leaves every losing round open for someone else's cleanup job to interpret. Ask any supplier how a zero-win round closes, and ask for the open-round count per studio on the reconciliation you receive. The one studio offline guide covers the neighbouring case, where the connector stops answering altogether.

Signals that the layer above the studios is thin

Symptom you can seeWhat it usually meansQuestion to send
Studio error codes appear in your logs unchangedNo mapping layer, so your wallet interprets each studio's codes itselfSend the mapping for the studios we enable, including codes added this year.
Every game reports the same typeCategories come from a studio-level field, so crash rounds and live tables are both casinoWhich fields are recorded per game, per table and per studio?
A currency is refused by one studio onlyThe studio's supported list was never normalised against your walletWhich of my currencies does each enabled studio accept at launch?
Game rows do not sum to the studio totalTwo studio accounts, or an adapter writing to its own tableDoes the reconciliation file tie to the studio invoice before it reaches me?
A title appears under two idsA reskin or regional build kept the studio's original game idWhich ids are unique across the catalogue you expose?

FAQ

Questions operators ask

How does a game aggregator work with my existing platform?

Your platform calls the catalogue and the launch endpoint, and it answers balance, debit, credit and rollback. Player accounts, payments and the lobby stay yours. You do not build a separate adapter for each studio.

Is there a fee each time we switch a studio on?

There should not be one, and if there is, it belongs in the fee schedule rather than on the first invoice. The commercial model is a share of GGR on the content, so enabling a studio changes your mix rather than adding a line. Ask for the schedule to list every charge that is not the share.

Can one studio's outage take down the rest of the catalogue?

It should not, because each adapter is its own connector. The practical test during an outage is whether the catalogue marks that studio unavailable while launches for every other studio keep working, and whether your lobby hides the affected tiles rather than leaving links that fail on tap.

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
  • GlossaryGame aggregatorA game aggregator links an operator to many studios through one integration, one contract, one shared wallet and one reconciliation file.Read
  • Guide · SelectionChoosing an aggregatorJudge an aggregator on market coverage, the wallet contract, reporting and exit terms, not on the size of the catalogue alone.Read
  • ComparisonAggregator vs directDirect integration is a separate project for each studio. An aggregator is one connection placed in front of many studios.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.

Telegram @turnkeyxhub WhatsApp Email Contact form