Guide · Operations
A new client is a release, even if the maths is the same
Studios replace clients to fix browsers, add languages or change a layout. The wallet contract usually stays. The things around it, certificates, launch behaviour and help text, sometimes do not.
7 min readUpdated By the Turnkeyxgaming team
Retest the frame, not the entire casino
When a version changes, check the launch inside your frame, the cashier return, the language you rely on, and the reality-check chrome over the top. A client that now uses a newer browser feature can break an in-app webview you forgot about. The debit and credit shapes should be unchanged. If they are not, that is an integration incident, not a cosmetic release.
If the certified build number changed, the certificate file should change with it. A silent maths change without a new certificate is a reason to pause the title. A cosmetic change with the same build number is a reason to smoke-test and move on. Ask which one you were given. Do not assume from the changelog headline.
Retest inside the webview you actually ship, not only in a desktop browser the studio used for the demo. A client that now needs a newer browser feature can launch, spin once, and then fail the cashier return or sit on top of your reality-check frame. The wallet contract should be boring: the same debit and credit ids, the same acknowledgement rules. If those shapes moved, stop and treat it as an integration change. A changelog that says 'visual refresh' does not prove they stayed put.
A regression that stays in proportion to the change
Ask whether the certified build moved before you decide how much to retest. The answer changes the list.
- Launch inside your frame, on the webview you ship. Open the cashier, return, and close.
- Confirm the language you rely on still loads, and that your reality-check chrome is still visible over the client.
- Confirm debit and credit ids are the ones your wallet already stores. A new field is an integration incident.
- If the build number changed, wait for the matching certificate before you leave the title generally available.
- If the build number did not change, smoke-test and move on. Do not recertify the whole catalogue because the art moved.
A short regression
- 01
Frame and return
Launch, open cashier, return, close. Do this on the webview you actually ship.
- 02
Same wallet
Confirm debits and credits still use the ids you already handle.
- 03
Build number
If the certified build changed, wait for the matching certificate.
The maths can stay still while the frame breaks
Most client replacements are browser, language or layout work. Players still reach them through your cashier link and your session frame. A wallet that has not changed can sit behind a return path that now does.
Release plan
A release window that does not need a war room
Treat a client update as a small release with a named owner. A week before, confirm the build number and whether a new certificate accompanies it. The day before, run the launch in staging inside your frame, open the cashier, return, and check the language and the reality-check chrome. On the day, enable the title for a small share of traffic first and watch debit errors, callback retries and cashier returns before opening it to everyone.
The rollback decision belongs to your team, not the studio. If the build number changed without a matching certificate, pause the title. If the frame or the return path fails, disable the title and keep the rest of the studio running. A visual refresh on the same certified build is a smoke test, not a recertification project, but it still needs someone to look at it on the devices you actually ship.
What to check, and when
| When | Check | If it fails |
|---|---|---|
| A week before | Build number and certificate scope | Hold the release until the matching certificate arrives |
| The day before | Launch, cashier return, language, reality-check frame in staging | Fix the frame or delay the release |
| Release day | Debit errors, retries, cashier returns on a small traffic share | Disable that title and keep the studio live |
| The day after | Settlement and reporting lines for the new build | Reconcile against the studio total before expanding traffic |
FAQ
Questions operators ask
Do we have to re-certify our platform when a slot client updates?
Usually you retest the integration, and the studio handles the game certificate. Your own platform certification, if you hold one, follows your regulator's change policy, which is separate.
Do we recertify our platform because a slot client shipped a new build?
Usually you retest the integration points you own, and the studio handles the game certificate. Any certification you hold on the platform follows your regulator's change policy. That policy is separate from the studio's lab report.
Should a visual refresh go through the same pause as a build-number change?
No. Same certified build: smoke-test the frame and the wallet ids. A new build number without a new certificate: pause the title. The changelog headline is not how you tell those apart.
Who decides to pause a title after a client update?
Name one owner before the release, usually the person accountable for the lobby or the integration. A studio contact can explain the change, but it cannot make the decision for your licence and your players.
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.
- eCOGRA
Independent testing and RNG certification for online gambling software.
ecogra.org
- UK Gambling Commission
Remote gambling and software technical standards.
www.gamblingcommission.gov.uk
Keep reading
Related pages
- Guide · ComplianceGame certificatesA lab certificate names one build, one RTP and one jurisdiction. It is not your licence, and it carries an expiry date you must track.Read
- Guide · ComplianceCertificate expiryWhen a game certificate expires, the title comes down. The operator cannot renew it; that signature belongs to the studio and the lab.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
- Guide · OperationsOne studio offlineIf one studio fails, mark that studio unavailable and leave every other studio launchable. A lobby-wide outage is a choice.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.