Glossary
A sandbox is a separate environment
The sandbox is where you try launches, failures and voids without creating revenue. It has its own credentials. Success there does not by itself prove production keys, production certificates or production latency.
3 min readUpdated By the Turnkeyxgaming team
Sandbox keys must never sit in a production config
Keep sandbox rounds out of the invoice, as the invoice guide describes. Do not point a sandbox cashier return at the production site. People do this once and fund a real account by mistake.
Some studio behaviours, especially live tables and progressive jackpots, are limited or absent in sandbox. A green sandbox test of slots is not a test of the live betting window.
What a green sandbox run does not prove
It does not prove live-table latency, jackpot behaviour, production allow-lists or the invoice path. Slots that work in sandbox can still fail the betting window of a game show.
Point sandbox callbacks at a sandbox wallet URL. The most expensive mistake is a production brand whose callback URL still ends in the staging host.
Store the sandbox brand as its own config: base URL, callback host, player accounts and encryption key. A key that is accepted in both places will be pasted into the wrong deploy on a Friday. The key guide is the split. This page is why a green test still needs a named environment on every export.
Before anyone calls the sandbox finished, run a void, a repeated debit and a loss that credits zero. A single winning spin only shows that a launch URL came back. The argument with finance is about the ugly rounds. If those three are not in the test log, the test log is a demo.
Read a sandbox pass as a narrow result
| A pass can show | It still leaves open |
|---|---|
| The launch URL returns for a test player | Production IP allow-lists and production certificates |
| Debit and credit land on the test ledger | That the production idempotency index uses the same key rules |
| A slot round closes | A game-show window with a full table of bets |
| Swapped keys are rejected | That nobody has pointed the live brand at the staging host |
| You can export a file | That the file is excluded from the billable GGR run |
Put the environment in the filename
A download named like a monthly invoice will be paid by someone who did not open the header. The sandbox export needs the word sandbox in the filename and in a column. The production job should be unable to pick that file up by accident.
A sandbox script with numbers to fail against
A test that produces a screenshot is not a test. Write the expected ledger after each call. Opening balance €1,000.00. A €1.00 spin that wins €2.40 should leave €1,001.40, because the stake returns inside the credit.
Then the ugly four. A losing spin: debit €1.00, credit €0.00, balance €999.00, and the round closed rather than pending. A duplicate debit: one debit, one balance, one round. A void: debit €1.00, rollback €1.00, balance back to €999.00 across two lines. A 100 times buy on a €0.20 base stake: a €20.00 debit, and a loss limit that moves by €20.00 rather than by twenty cents.
Every one of those has an expected number, so the run fails visibly instead of passing because a page loaded. Run the same script once against production with a single minimum-stake round before launch, and compare the two result files line by line.
Six scenarios and the balance each leaves
| Scenario | Calls | Expected balance from €1,000.00 | Round state |
|---|---|---|---|
| Win €2.40 on a €1.00 spin | debit, credit | €1,001.40 | Settled |
| Loss on a €1.00 spin | debit, credit 0 | €999.00 | Settled at zero, not pending |
| Duplicate debit | debit, debit | €999.00 | One round, one debit |
| Void | debit, rollback | €1,000.00 | Voided, two lines |
| Lost response, then retry | debit, retry | €999.00 | One debit, replayed response |
| 100× buy on a €0.20 base | debit €20.00, credit | Depends on the feature, and the debit is €20.00 | One round with a €20.00 stake |
What the test log must record for each scenario
- The request and response bodies, with the transaction id visible in both.
- The balance before and after, exactly as the wallet returned them.
- The round id, and whether the state moved from pending to settled.
- The HTTP status, and how many attempts the client needed to get it.
- A timestamp with a timezone, so a run repeated a week later can be matched to an invoice query.
- The environment, written into every line rather than inferred from the filename.
FAQ
Questions operators ask
Can we performance-test the sandbox and treat it as production capacity?
No. Capacity, allow-lists and data are different. Run a production-shaped test against the environment you will actually operate, under an agreed window.
Do sandbox rounds appear on the GGR invoice?
They must not. If they do, the environment split has failed. Reconcile sandbox keys out of the production file before you pay or query the invoice.
Can finance rehearse the monthly file in sandbox?
Yes, if the rehearsal file is marked sandbox and is never concatenated onto the production invoice. The columns have to match the production export. A cleaner test spreadsheet that someone later 'maps across' is how play-money stake reaches the bill.
Can we test live tables in the sandbox?
Expect limits. Live tables need a dealer, a table and a schedule, so test access is often restricted to selected tables at selected hours, and progressive jackpots may be absent or held in a fixed state. Ask which live titles are available before promising a client a full test, and test the betting window specifically.
How long is sandbox data kept?
Agree it in writing at onboarding, because retention is not something a supplier can promise on a studio's behalf. Anything you need as evidence has to be exported before the window closes. A report built on sandbox history and left running into production is how test GGR appears in a monthly figure.
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
- Guide · IntegrationTwo sets of keysWhy sandbox and production credentials must differ, how to rotate them, and how a key ends up in the wrong config on a Friday.Read
- IntegrationIntegrationSandbox keys, AES-encrypted wallet callbacks and the four wallet endpoints, then a 24–72 hour go-live once decryption and retries pass.Read
- DocumentationAPI docsAuthentication, the game list, demo and real launch, AES-encrypted wallet callbacks and error handling, with test keys to start.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.