Turnkeyxgaming

Guide · Compliance

An expired certificate means the title comes down

Certificates end. The studio renews them with the lab. You cannot renew them yourself, and you should not keep a tile up on a promise that the PDF is 'on its way'.

7 min readUpdated By the Turnkeyxgaming team

Diary the date against the catalogue id

Store the end date on the game id you actually launch. A spreadsheet of marketing names will miss a reskin. Thirty days out, ask for the renewal. On the end date, hide the title if the new certificate is not in hand. Leave the rest of the studio up. Players with an open round can finish or be voided under the studio's instruction. New launches stop.

A renewal sometimes changes RTP or build number. When it does, update the figure you display and retest the client. When it does not, file the PDF and restore the tile. Do not show a grace period you were not granted. If a regulator in that market allows a grace period, it will say so to you, and counsel should be the one who tells operations.

Key the diary to the game id you launch. A spreadsheet of marketing names misses a reskin that carries its own end date, and a studio-level date hides the one title that actually lapsed. Thirty days out, ask the studio for the renewal and record who answered. On the end date, with no PDF in hand, stop new launches of that id and leave the rest of the studio up. Open rounds finish or void under the studio's instruction. They are not a reason to keep the tile available to everyone else.

The diary entry for one game id

Expiry is a date on a catalogue row. The work is to make that date do something on the day, without taking the whole studio with it.

  • Store the end date on the game id you launch, not on the name printed in the lobby.
  • Ask for the renewal ahead of the date, and keep the answer with the old PDF.
  • On the day, if the replacement is not in the folder, stop new launches of that id.
  • Leave every other title from the studio enabled. One lapsed page is not a studio outage.
  • If the renewal changes the build or the RTP you display, update the tile and retest before the title returns. If it changes neither, file it and restore the tile deliberately.

The expiry day

  1. 01

    Hide launches

    Stop new launches of that game id when the certificate ends without a replacement.

  2. 02

    Keep the studio

    Do not disable every title from the studio because one PDF lapsed.

  3. 03

    Update the figure

    If the renewal changes RTP or build, change the tile and retest.

A promise that the PDF is on its way is not a certificate

You cannot sign a renewal for the studio, and you cannot keep the tile up on an email that says the lab is busy. New launches stop. The title returns when the page is in the folder and, where the build moved, the tile matches it.

A register answers the question a folder cannot

A folder of PDFs sorted by studio answers which studios are current. The question that arrives from operations is narrower: which of the titles on this brand's European row carry a report that ends before the quarter does. That is a query across rows, and a folder cannot run it. Keep a register keyed on the game id you launch, holding the studio, the build the report names, the lab named on it, the report's own reference transcribed from the document, both dates, the last renewal request and who answered it.

Two fields do more work than the rest. The build id tells you whether a renewal actually covers the client that is live, because a report for an older build describes a game you are not running. The date of the last request, with a name beside it, separates a slow lab from nobody having asked.

The register also settles the restore question before it arises. Decide who may bring a title back, on what evidence, and state that a catalogue sync or a routine deploy is not that decision. The common failure is a title returning because an import rewrote the enable flag, discovered by the person who disabled it, by which time players have been on it for a day.

Four states a title can be in, and the only action each allows

The state is a row in the register, not a memory of an email thread.

StateNew launchesWhat the register must show
Report current, build matchesAllowedBoth dates, the build, and the reference transcribed from the report
Renewal requested, current report still in dateAllowed until the date printed on itWho asked, when, and what they were told
End date passed, nothing filedStopped for that game idThe date it stopped, and the ticket that hides it
Replacement filed, build changedAllowed once the tile matches the new buildThe retest, the return figure shown, and who restored it

FAQ

Questions operators ask

Can Turnkeyxgaming extend a lab certificate?

No. Only the studio and the lab can renew it. We can disable the title for your brand while that happens.

Can we extend the end date ourselves while the studio chases the lab?

No. Only the studio and the lab can renew the page. Operations can hide the game id for the brand until the replacement arrives. Inventing a grace period the document does not contain keeps an uncertified build in the lobby.

Do open rounds have to be voided at midnight on the expiry?

No. Stop new launches. Rounds already open finish or void under the studio's instruction for that incident. A local policy that refunds every open round at midnight will not match the settlement the studio still sends.

The studio says the renewal is with the lab. May the title stay up?

While the current report is inside its dates, the title is certified until the date printed on it and the email changes nothing. The day after that date, the only question is whether a replacement is in the folder. Diarise the date rather than the promise, and give whoever owns the row a way to see it coming.

Do we need one register per brand, or one for the group?

One register with a brand column usually carries the document, because the report itself is the same file. The decision to hide a title is per brand, so record the brand-level action too. A group entry hides the fact that one brand stopped launching on the Tuesday and another did not.

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

  • Malta Gaming Authority

    Licensing and player-protection rules for Malta-licensed operators.

    www.mga.org.mt

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 · LobbyShowing RTPShow the RTP of the build this brand is running, not a studio average and not another certified setting from a different market.Read
  • StudiosStudios300+ studios across slots, live casino and instant games, switched on per licence rather than as a blanket. A name here is not a promise.Read
  • Guide · OperationsNew game clientsA new game client is a release even when the maths is unchanged: retest launch and certificates, and leave the wallet alone.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