Turnkeyxgaming

Guide · Lobby

Demo mode is a studio setting, not a right

Demo play lets a visitor spin without a wallet. Some studios allow it. Some disable it for jackpots, live tables or particular markets. You cannot promise a demo button on every tile.

7 min readUpdated By the Turnkeyxgaming team

Demo stake is not revenue

A demo session should never call the production wallet. If it does, you have built a hole. The client either runs a local demonstration or uses a studio demo endpoint that cannot debit a real player. Live tables often have no meaningful demo, because there is no dealer performance to fake without a stream. Hide the button when the catalogue says demo is unavailable.

Do not use demo as a way to avoid a licence conversation. A demo that is shown to consumers in a market where you cannot offer the real game can still be a problem. Ask counsel. And keep demo sessions out of the GGR file entirely. They are not zero-stake production rounds. They are not rounds.

Treat a missing flag as unavailable. Some catalogues omit the field instead of sending an explicit no, and a button that defaults to on will call a demo endpoint that does not exist or, worse, the real launch. Live tables usually have nothing honest to demonstrate, because a recorded shoe is not the betting window the player would join. Hide the control. Do not substitute a trailer and label it play.

Before the demo control is rendered

The button is a claim that this title can be tried without a wallet. Confirm the claim per game id, not per studio.

  • The catalogue says demo is available for this title. A studio-level guess is not the flag.
  • The session cannot reach the production wallet. A local demonstration or a studio demo endpoint that cannot debit a real player are the acceptable shapes.
  • Live tables without a flag do not get a recording in the button's place.
  • Demo activity is dropped before the revenue export. It is not written in as zero-stake rows.
  • The market question is settled with counsel where you cannot offer the real game. The button is not a workaround.

A safe demo button

  1. 01

    Catalogue flag

    Show demo only when that title says it is available.

  2. 02

    No wallet

    Confirm a demo session produces zero production wallet calls.

  3. 03

    Leave revenue

    Drop demo activity before the GGR export, not inside it as zeroes.

A demo that debits production is a hole, not a feature

If a visitor without an account can move a real balance, the launch went to the wrong endpoint. Stop the button for that title until a session produces no production wallet calls at all.

A demo tile that reached a real wallet through a campaign page

A campaign page linked straight to the launch endpoint with a demo parameter in its own query string and no account behind it. The lobby's flag check never ran, because the lobby was not in the path. The endpoint treated the missing player as a guest and created one against a wallet that shares a database with production and differs only by a secret. Over one weekend, 118 visitors produced roughly 3,000 rounds signed with the production key.

The failure is architectural rather than cosmetic. A demo control enforced in the lobby component is enforced in one of five ways into a game. The launch endpoint has to refuse a demo request unless it can see the catalogue flag and a credential that is permitted to ask for demo. A landing page is a client like any other and should not be able to talk the API into a session shape the lobby would have declined.

Check what a demo session writes. It should produce nothing in the wallet and nothing in the billable file, and the absence should be provable by searching for the session id rather than by trusting a filter somebody wrote once. If the studio's demo endpoint needs a guest account, give it a namespace of its own, exclude it by construction and give it a balance no report reads. A guest holding a funded balance is a production player with a friendlier label.

Four doors into a game, one flag to test

Each of these has been the hole on some integration. Test the refusal, not only the happy demo.

  • The lobby tile, the search result, a campaign landing page and any shared deep link, all with demo switched off in the catalogue for that title.
  • The launch endpoint asked directly with a demo parameter, using a credential from the wrong environment. It has to refuse rather than negotiate.
  • The wallet log and the billable file searched for the demo session id afterwards. Zero rows is the pass condition, and it takes a minute.
  • The guest account, where the studio requires one: its namespace, its balance, and the report that excludes it by construction rather than by a predicate.
  • The catalogue flag for the title itself, read per game id, because a studio-level assumption is not a flag and jackpot entries are the usual exception.

FAQ

Questions operators ask

Why do some live tables have no demo?

Because the product is a real table with a betting window. A recording would misrepresent the game. The studio's flag is the answer for each title.

Can staff use demo mode to reproduce a production wallet bug?

No. Demo never calls that wallet, which is the point. Reproduce wallet bugs with sandbox credentials and a test player. Demo is for visitors spinning without a balance.

Should a jackpot title offer demo when the rest of the studio does?

Only when that title's own flag says so. Jackpot and live entries are the ones studios most often switch off. Inheriting the flag from a neighbouring slot puts a button on a game that has no demo endpoint.

Marketing wants a public demo page with no login. Is that the same risk as the button?

The same product with a wider door. If the page calls the launch endpoint, that endpoint needs the catalogue flag and an unprivileged credential. If it embeds something the studio hosts, find out what the embed can reach before the address appears in a paid campaign, because an embed is a session you did not mint.

Should demo rounds appear in a logged-in player's history?

Only if the player used the demo while signed in, and even then they are not money. A demonstration win listed beside a real balance invites a comparison, then a withdrawal attempt, then a ticket. If you show the list at all, separate it from the money view and label it so nobody mistakes one for the other.

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.

Keep reading

Related pages

  • Guide · TestingSandbox versus invoicesHow to separate sandbox players, test currencies and staff accounts from the GGR file that becomes an invoice, with examples.Read
  • Product · Live dealerLive casinoRoulette, blackjack, baccarat, game shows, teen patti and andar bahar on one dealer-table wallet and one GGR report, per licensed market.Read
  • Guide · FinanceThe daily GGR fileThe daily GGR file agrees stake, win and the difference in one closing timezone, with bonus-funded wins marked for reconciliation.Read
  • 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

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