Who this page is for
An operator drawing up the content list for a new casino, or adding and replacing studios on a live one. The short answer: run four filters in order. First, does the studio hold what your licence asks of suppliers? Second, is its test report from a lab your regulator accepts? Third, which RTP version is certified for which market? Fourth, do you reach it through an aggregator or a direct contract? Studio reputation and game count come after all four, because a studio that fails the first filter gives you no games at all.
The integration itself, meaning the wallet callbacks, launch URLs and certification run, is on the online casino API page. This page is about which studios to ask for and what to ask them.
The four filters, in order
Each row removes studios. The right-hand column is where the answer is written down, so you can check it yourself rather than take a sales deck's word for it.
| Filter | What to ask the studio | What fails it | Where the answer is written |
|---|---|---|---|
| Supplier authorisation | Do you hold the supplier licence or certificate my licence requires? | Anjouan has required a B2B licence or Recognition Certificate (€9,500 a year) from every supplier since 1 July 2025. Ontario requires anyone supplying games or game systems to igaming operators to be registered with the AGCO. Finland allows only software from a Finnish gambling software licence holder from 1 July 2028. | The regulator's register or the certificate itself, dated |
| Test report | Which lab tested this game, under which standard, for which market? | A report from a lab outside the regulator's accepted list. Curaçao accepts labs accredited to ISO/IEC 17025 with online gaming, RNG, fairness and RTP in scope. The UK keeps a list of approved test houses. Brazil recognises certifying bodies one ordinance at a time. | The lab's certificate, naming the game version and RTP |
| RTP version | Which RTP versions exist, and which is certified where? | Enabling a version that has no certificate for that market | The studio's game sheet and the per-market certificate |
| Route to market | Aggregator or direct, and who answers when a round breaks? | A direct contract you cannot staff, or an aggregator that does not carry the studio for your licence | Your contract and the aggregator's jurisdiction matrix |
Tobique sits at the other end: suppliers do not need a B2B licence to serve its licensees. That is a lighter supplier filter, not a missing one. Studios still apply their own jurisdiction lists.
One game, several RTP builds
Many studios ship the same title at several return-to-player settings and let the operator choose. Hacksaw Gaming's page for Wanted Dead or a Wild lists four: 96.38%, 94.55%, 92.33% and 88.42%. The setting is a commercial decision, and taxes push it. The UK raised Remote Gaming Duty from 21% to 40% on 1 April 2026, which gives every UK operator a reason to look again at the setting.
Two things follow for your launch list. Certificates are per version, so the version you enable in each market must be the one tested for it. And the RTP shown to players must match the build that is running. Ask for RTP per game and per market in the content matrix, not one figure per studio.
Market rules that change the game, not just the list
Some regulators write rules into the game cycle itself. Studios then ship a market build, so players in one country do not see the build that runs elsewhere. We do not file licences in the UK or Germany. They are here because studios build to their rules, and those builds reach other markets.
| Market | Rule on the game | What it means for your list |
|---|---|---|
| United Kingdom | Online slots stake capped at £5 per game cycle from 9 April 2025, and £2 for players aged 18 to 24 from 21 May 2025. At least 2.5 seconds between slot game cycles (RTS 14D). No turbo, quick spin or slam stop (RTS 14E). No celebrating a return at or below the stake (RTS 14F). | A UK build per game, and a platform that knows each player's age band before the first spin |
| Germany | Virtual slot stakes capped at €1 per game, an average game length of at least five seconds, no autoplay, no pooled jackpots, and one game at a time (GlüStV 2021, §22a) | Jackpot titles drop out entirely; other titles need a German build |
| Finland, from 1 July 2027 | No acquisition bonuses; retention bonuses only, with wagering capped at 5× | No game is removed, but free-spin campaigns built for other markets cannot run there |
| Anjouan | Restricted list covering the US, UK, France, Germany, Spain, the Netherlands, Austria and Australia, among others | Studios that accept Anjouan still apply their own country blocks on top |
Aggregator or direct contract
An aggregator gives you many studios through one integration and one invoice. A direct contract gives you one studio, its own integration and its own commercial terms. Most operators launch on an aggregator and go direct only for the few studios that carry the most revenue.
| Through an aggregator | Direct with the studio | |
|---|---|---|
| Integration | One wallet integration for every studio behind it | One per studio, each with its own certification run |
| Supplier checks | Check the aggregator and each studio behind it; one does not cover the other | One studio to check |
| Commercial terms | The aggregator's rate card, with the studio's fee inside it | Negotiated with the studio, which matters once a studio carries a large share of GGR |
| Reconciliation | One statement across studios | A statement per studio, matched against your own ledger |
| Incidents | The aggregator triages, then escalates to the studio | You talk to the studio's support directly |
| Leaving | Every studio behind it leaves with it unless you hold direct contracts | Only that studio is affected |
Our aggregation runs on the casino API. A studio you already hold a direct contract with can sit behind the same wallet integration, so your cashier stays single-balance either way.
Who should not start with a studio list
- Operators who have not chosen a licence. The licence sets the supplier rules and the restricted countries, so a studio list drawn up first gets redrawn. Start at gambling licensing.
- White label brands. The studios are the ones connected to the licence holder's licence. You choose from that shelf; you do not build it. See white label casino.
- Anyone comparing aggregators on headline game counts. The number that matters is what survives the four filters for your licence and markets.
Where launch lists go wrong
- A studio signs, then cannot serve the licence. On Anjouan a supplier without the Recognition Certificate cannot legally serve your brand, whatever its contract says.
- The wrong RTP version goes live. The game was certified at one setting for that market and enabled at another. It surfaces at audit or in a player complaint, not at launch.
- The UK build is the only build. UK cycle-speed and stake rules are stricter than most offshore markets need. Taking the UK build everywhere costs you features you are allowed to offer; taking a non-UK build into a UK-facing product breaches RTS 14.
- Live dealer is missing at launch. Live studios keep the strictest jurisdiction lists, and players notice the gap first.
- A jurisdiction list changes mid-contract. Studios withdraw from markets. Your contract should say who tells whom, and how quickly the games come down.
Questions to put to any provider, including us
- For my licence and market list, which studios pass, and which fail on supplier authorisation?
- For each game, which RTP versions exist and which is certified for each of my markets, by which lab?
- Does the aggregator hold its own supplier authorisation where my licence requires one, separately from the studios?
- When a studio withdraws from one of my markets, how am I told, and how fast are the games removed?
- Can a studio I contract directly sit behind the same wallet integration?
- Who holds the round history when a player disputes a result: me, the aggregator or the studio?
Frequently asked
Do you publish a list of the studios you carry?
Not as a headline. Which studios you can run depends on your licence, your markets and the RTP versions certified for them, so we run that check at scoping and give you the list for your case in writing.
Is a game certified once for every market?
No. A test report covers a game version under a standard, and regulators decide which labs and standards they accept. Curaçao accepts labs accredited to ISO/IEC 17025 with gaming systems, RNG, fairness and RTP in scope; the UK requires an approved test house before release. Ask for the certificate per market.
Can we choose a lower RTP to protect margin?
Where the studio offers a lower certified version for your market, yes, and it is common. Display the RTP of the build that is actually running, and expect players and affiliates to compare settings between operators.
Do studios need anything from Anjouan or Tobique?
Anjouan, yes: a B2B licence or Recognition Certificate at €9,500 a year, required since 1 July 2025. Tobique, no: its B2B licence is voluntary, so suppliers can serve Tobique licensees without one.
Should we go direct with our biggest studios from day one?
Usually not. A direct contract adds an integration, a certification run and a reconciliation stream. It pays once a studio carries enough GGR for its own rate to matter, which you only know after launch.