RNG Certification: A Checklist Before You Submit Your Game
What testing labs look for in random number generation, and the small mistakes that send games back for another round.
Certification delays are expensive. Every round trip with a testing lab can cost weeks, and many rejections come down to issues that are simple to fix before submission.
Before you submit
- Use a certified RNG library and document its version and seeding
- Keep RNG calls on the server, never in client code
- Map random numbers to outcomes without modulo bias
- Log every game round with enough data to replay it
- Make sure the math model document matches the build exactly
The math model is part of the game
Labs will simulate millions of rounds and compare the measured RTP and hit frequency with your documentation. If a late design change adjusted a reel strip and nobody updated the PAR sheet, the game fails.
Build for the next submission too
Most studios will reskin a successful slot many times. Keeping math, RNG and presentation cleanly separated means a reskin only needs a lighter review instead of a full certification.
Working on something similar?
We are happy to share what we know. A first call costs nothing and comes with no obligation.
Talk to an engineer
