Certification is the mandatory step between a finished game and its appearance in an operator's lobby on a regulated market. The work is done neither by the regulator nor by the operator, but by an independent test laboratory accredited by the regulator of the jurisdiction in question. Its remit is to confirm that the game behaves exactly as the documentation says it does, and that it meets the requirements of the market it is destined for.
What is actually tested
The primary objects of the review are the random number generator and the mathematical model. The lab assesses the statistical properties of the RNG output, the reproducibility of payout calculations, and whether the observed RTP matches the figure declared in the game's specification. Behaviour under abnormal conditions is examined separately: dropped connections, re-entry into a session, a round left unfinished.
- the game maths and the rules by which wins are awarded;
- RNG operation and the way it is seeded;
- correct display of the rules and of the paytable;
- round logging and the ability to reconstruct a round after the fact.
Why a certificate is not universal
Requirements are set by the jurisdiction, not by the laboratory, which is why the same product goes through testing again for every market. Permitted RTP ranges differ, as do rules on forced pauses and on-screen warnings, the treatment of autoplay, and reporting formats. Some markets accept reports issued by labs accredited elsewhere; others insist on the full local procedure regardless of what has already been done.
How this shapes the release cycle
Certification is built into the release plan from the outset, because changing the maths after testing generally means testing again. Studios therefore split changes into those that touch the certified part of the build and those that do not: artwork and localisation usually pass through a lighter procedure, while anything affecting the RNG, the paytable or the bonus logic restarts the process.
For the operator, the certificate is not paperwork but the condition on which the game can be connected at all, and a standing item in the compliance file.
