Guide · Catalogue
Block a title without switching off the studio
Markets rarely ban an entire studio and permit everything else, or the reverse. The usual job is narrower: this title, this country, this brand. The catalogue has to express that without a redeploy.
7 min readUpdated By the Turnkeyxgaming team
Decide which country you mean
Account country and IP country answer different questions. A licence often cares where the player is, which is a geo signal, and also where they are registered. If those disagree, your policy has to say which one hides the tile. Hiding on registration country alone leaves a traveller inside a market you do not hold. Hiding on IP alone surprises a resident on a corporate VPN. Write the rule, then implement that rule.
The player should see a short reason, not a broken image. 'Not available in your location' is enough. Removing the game from search and from deep links matters as much as removing it from the row. A shared URL from another country should fail politely. The rest of that studio stays. One blocked title is not an outage.
Store the block against the game id, the brand and the country signal you chose, and read it at render and at launch. A lobby cache on a phone can keep a tile for hours. The launch call is what stops the session, with the same short reason, rather than a client that loads and then fails on the first debit. Favourites and the recent-games strip use that launch check too, or the tile you hid in the row is still one tap away.
Which country signal hides the title
Pick the signal in the policy note, then make every entry point use that signal. A second, quieter rule in the launch path will not match the lobby.
| Signal you documented | Who loses the tile | Who still sees it |
|---|---|---|
| Account country only | Players registered in the blocked market. | A traveller physically in that market, and a resident whose IP is elsewhere. |
| IP country only | Connections that geo-locate there, including some VPNs and some travellers. | A resident on a corporate VPN that exits somewhere else. |
| Both must be clear | Anyone whose account or whose current IP is in the blocked market. | Only players who match on neither. This is the stricter of the two tests. |
| Brand plus country | That brand's players in that market. A sister brand is untouched. | The same title on a brand whose approval still covers it. |
A precise block
- 01
Name the signal
Document whether IP, account country or both must match before the title shows.
- 02
All entry points
Apply the block to rows, search, favourites and direct launch.
- 03
Leave the studio
Do not disable the studio's other games unless the approval says to.
One title is not a studio switch
Disabling the studio because a single game is uncomfortable in one market takes down tables and slots the approval never mentioned. The block names a game id. The rest of that studio's catalogue stays launchable.
Every entry point has to agree
| Entry point | What the player sees | Where the rule is checked |
|---|---|---|
| Lobby row | Title absent | Catalogue rendering for the brand and signal |
| Search result | Title absent or marked unavailable | The same catalogue filter |
| Favourites | Short unavailable message | Launch check, not only the tile |
| Shared link | Short unavailable message | Launch check before a session is created |
FAQ
Questions operators ask
Will the aggregator geo-block consumer traffic for us?
You still decide the rule for your licence. The catalogue can omit a title for a brand and market. Your platform should enforce it at launch as well.
Does a country block void rounds that are already open?
No. It stops new launches of that game id for the signal you chose. An open round settles or voids under the studio's ordinary rules. Pulling the stake back because the player crossed a border mid-session is a different policy, and it is not this switch.
Should the shared URL show a login wall instead of the reason?
No. A player who can already launch other games should see that this title is unavailable in their location. A login wall implies the game is fine and the session is the problem. Search, favourites and the direct link all use the same sentence.
Does the block apply to the whole studio?
No. It applies to the game id and the country signal you documented. Disabling the studio would remove tables and slots the approval covers, which is a different decision and a bigger outage.
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
- UK Gambling Commission
Remote gambling and software technical standards.
www.gamblingcommission.gov.uk
Keep reading
Related pages
- Product · Casino APICasino APIThe casino API is one contract — a catalogue, a launch call and wallet callbacks — built once and reused for every studio we connect.Read
- Guide · CatalogueDisabling one titleHow to take a single game out of the lobby, search and launch while leaving the rest of that studio available to players.Read
- GlossaryGeoblockA geoblock refuses a product by location. IP country, the registered address and GPS often disagree on where the player actually is.Read
- Region · WorldwideWorldwideOne integration, a catalogue per market and multi-currency wallets, at 13% of GGR in Asia and 16% elsewhere, region by region.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.