TST Certification for Online Casino Games
TST certification is a historical testing credential linked to Technical Systems Testing, an independent laboratory acquired by Gaming Laboratories International (GLI) in 2010. It indicates that specified gaming software or systems underwent technical assessment against an identified standard; it does not guarantee wins or make every product on a site certified. For Canadian players, the approving jurisdiction matters more than the seal alone. In Ontario, games and random number generators must be certified against the Registrar’s Standards for Internet Gaming by an independent testing laboratory registered with the Alcohol and Gaming Commission of Ontario (AGCO). This glossary explains the scope, checks and practical limits of TST certification.

How TST Certification and Testing Developed
TST certification documents that a defined gaming product passed tests against a specified technical standard. Technical Systems Testing examined interactive gaming systems, wagering technology and game software before GLI acquired its assets, intellectual property and trade names in 2010. The credential applies only to the tested version and scope. It should not be read as a blanket approval of an operator, every available game or future software updates.
Core Testing Areas
Core assessment covers RNG implementation, game mathematics, payout logic and system controls. Engineers review source code, statistical output, rules, paytables, bonus triggers, jackpot behaviour, accounting records and security functions as the applicable standard requires. RNG analysis checks whether outcomes are unpredictable and suitably distributed; theoretical return to player is calculated from probabilities and awards rather than promised for a short session. Material software changes can require impact analysis or renewed certification. Audit scope and jurisdiction therefore matter more than a seal displayed without a report number.
TST Certification in Regulated Canadian Gaming
Canada does not use one nationwide TST approval for online casino games. Provincial and territorial frameworks determine which technical standards, laboratories and distribution channels apply. In Ontario’s regulated internet-gaming market, the AGCO registers independent testing laboratories, while iGaming Ontario conducts and manages the commercial market. Games and RNGs must receive certification against the AGCO Registrar’s Standards before deployment. GLI is an AGCO-registered laboratory; a historical TST mark alone does not establish current Ontario authorization. Players should verify the operator’s provincial status and treat laboratory documentation as product-specific evidence, not a substitute for regulatory registration.
Reading TST Certification Claims Correctly
A certification claim is useful only when its scope, standard and software version can be verified. Check whether the document names the game, platform component or RNG, then confirm the issuing laboratory and target jurisdiction. Match report identifiers and dates where documentation is available. Certification supports technical fairness, but it does not turn RTP into a session forecast: a 96% theoretical RTP describes a long-run mathematical expectation, not a promise to return $96 from each $100 wagered. Bankroll limits, time limits and other responsible-gambling controls remain necessary because independent outcomes can still produce substantial short-term losses.
| Testing Component | What Is Assessed | What It Establishes | Typical Trigger |
|---|---|---|---|
| RNG evaluation | Algorithm, seeding and statistical output | Unpredictable, properly distributed outcomes | Initial approval or material change |
| Game mathematics | Probabilities, paytable and theoretical RTP | Rules and return model calculate correctly | Each game or math revision |
| Functional testing | Wagers, wins, features and error handling | Software follows approved game rules | Release and relevant update |
| System controls | Security, logging, accounting and access controls | Transactions and changes remain traceable | Platform approval or material change |
| Change review | Differences from the certified software version | Whether additional testing is required | Every proposed software modification |



