Turnkeyxgaming

Glossary

A game certificate is a lab report on one build

A game certificate records that a test lab examined a named build against a named standard. It has a jurisdiction and an end date. It is not your operating licence and not a brand-approval letter.

3 min readUpdated By the Turnkeyxgaming team

Match the PDF to the build you launch

Operators collect certificates during onboarding and when a build changes. The reading guide walks the fields. The expiry guide says what to do on the end date. Studios commission the labs. Aggregators do not sign the report.

Keep the file next to the game id you launch. A certificate you cannot match to a build is a PDF, not a control.

What to do on the expiry date

A certificate with an end date is not decorative. Before that date, ask the studio for the renewal or take the game down. Leaving it up because the previous file 'probably still applies' is how a regulator finds a build you cannot evidence.

Store the file against the game id, the build hash or version the lab named, and the jurisdiction. A folder of PDFs named by studio is not a control if you cannot tell which build is in production.

A patch release and a file that names the previous build

The certificate names build 1.4.1 at a 96.2% return. On 3 May the studio ships 1.4.2 with a currency-symbol fix and no change to the maths. The compliance folder still says 1.4.1 and the launch record says 1.4.2.

That gap is the finding, whatever the size of the change. Either the studio confirms in writing that the report covers the new build, or that a technical amendment does, or you are running an unevidenced build in a market that requires evidence. The size of the diff is not the test. The build identifier is.

Multiply by portfolio and the calendar becomes the risk. If 240 titles are certified for one market and they happened to be certified in the same quarter, the renewal workload arrives as 240 files in one month rather than twenty a month. Spreading the dates is a launch decision; after the deadline it is an outage decision.

What one certificate does and does not evidence

QuestionAnswered by the file?Where the answer actually lives
The return of this buildYes, for the named buildThe report, matched to the game id you launch
Your licence to offer itNoYour own licence and the market's rules
Your brand's approval in that marketNoThe market's process, not the studio's document
The generator testYes, for that buildThe report's section, cited rather than paraphrased
The jackpot configuration you enabledOnly where it is namedA separate written confirmation from the studio
A live dealer table's studio setupUsually notThe live supplier's own evidence

Where certificate control fails an audit

  • Files are stored by studio, so nobody can say which build is in production on a given brand.
  • A laboratory report is described as a licence in a marketing post, which the lab did not issue.
  • An expiry date passes and the game stays live because renewal was expected rather than received.
  • One market's report is used in a second market without a written confirmation quoting the second jurisdiction.
  • A title is patched on a Friday and the register of live builds is updated by nobody until the following month.

FAQ

Questions operators ask

Does one certificate cover every market?

No. Markets that require their own testing need their own evidence. A Malta report does not silently satisfy a different regulator.

Does the aggregator sign the certificate?

No. The lab signs it and the studio commissions it. We pass on the files studios provide. We do not become the lab.

Who commissions the certificate, the operator or the studio?

The studio normally, and the lab issues it to them. You hold a copy and the register that maps it to a game id, a brand and a market. If a supplier says an aggregator certificate covers you, ask for the document with your brand or jurisdiction named on it, because that is the version a regulator will ask for.

Does a build with no maths change need new evidence?

Ask the studio in writing rather than deciding from a release note. Some changes are covered by an amendment or by a confirmation that the build remains inside the tested envelope, and others are not, and the market may have its own view. The written answer is what an auditor reads, not the changelog.

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 · 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
  • GlossaryRNGA certified random number generator decides software results. A live wheel or a dealt shoe is a different source of outcomes.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

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