Getting a casino slot certified in Australia is one of the most complex regulatory undertakings in the global iGaming industry — and also one of the most valuable, given Australia's status as the first regulated Australian iGaming market and the likely template for provincial expansion. After guiding 47 titles through the certification process across multiple jurisdictions, we've distilled the process into a step-by-step guide that every Australian studio developer should read before writing their first line of production code.
Step 1: Choose Your Jurisdictions First
Certification strategy should drive architecture decisions, not the other way around. Each jurisdiction has different requirements, and building to the strictest common denominator from the start is far cheaper than retrofitting. For a Australian studio, the relevant jurisdictions are typically: ACMA (Australia), KAHNAWAKE, UKGC (if targeting UK operators), and MGA (Malta, for European distribution). We recommend targeting ACMA + KAHNAWAKE + UKGC as a baseline — the overlap covers 80% of the commercially relevant regulated markets accessible from Australia.
Step 2: Select a GLI-Approved Test Lab
ACMA mandates that all slot games be tested by a GLI-approved laboratory before going live in Australia. The major labs operating in Australia are GLI itself (Gaming Laboratories International), BMM Testlabs, and iTech Labs. Lab selection matters more than most studios realise. Turnaround times vary significantly — from 4 weeks to 14 weeks depending on the lab's backlog and your submission quality. BMM has a dedicated Australian office and shorter average turnaround for Australia submissions. GLI is the industry default and has the broadest acceptance across jurisdictions. We recommend getting quotes from at least two labs before committing.
Step 3: Prepare the Technical Submission Package
The submission package is where most first-time studios lose weeks. A complete GLI-11 submission includes: full source code with build instructions, RNG architecture documentation, math model documentation (paytable, hit frequencies, RTP simulation results), game rules documentation in plain English, responsible gambling feature documentation, and a completed GLI self-assessment checklist. Incomplete packages are returned without review — and the clock on your timeline resets. We maintain a submission package template that has passed on first submission 23 consecutive times. If you need help building yours, contact our regulatory team.
Step 4: RNG Pre-Certification
Before game-level certification, your RNG must itself be certified. If you're using a third-party RNG library that is already GLI-certified, you can reference that certification in your submission. If you've built a custom RNG (as we have), it requires its own certification submission. This is a one-time cost — once your RNG is certified, you can reference that certification across all future game submissions.
Step 5: Internal Pre-Submission Testing
Run the NIST SP 800-22 statistical battery against your RNG output internally before any lab submission. Run a minimum of 10 billion spin simulations against your math model and verify RTP convergence within ±0.1% of theoretical at 1 billion spins. Document any edge cases in your responsible gambling features — lab testers specifically look for scenarios where player-set limits can be circumvented.
Step 6: Regulatory Registration (ACMA)
GLI certification alone is not sufficient for Australia. Studios must also register as a "Registered Gaming Supplier" under ACMA's framework. This requires: corporate entity registration in Australia or another Australian province, a criminal background check on company directors, a description of your game development practices, and confirmation that your technical infrastructure meets ACMA's hosting and data residency requirements. Registration processing time at ACMA is currently 8–12 weeks. Apply in parallel with your lab submission to avoid dead time.
Step 7: Operator Integration and Go-Live
Once certified and registered, your game must be integrated with an ACMA-licensed operator or aggregator platform to go live in Australia. The integration process — including technical certification of the integration itself — typically adds another 2–4 weeks. Maintain a relationship with your platform integration team throughout the certification process so they're ready to move quickly once approvals land.
Total Timeline Expectations
For a well-prepared first submission targeting Australia + KAHNAWAKE, a realistic end-to-end timeline from submission to live game is 14–20 weeks. Poorly prepared submissions that require resubmission can easily extend to 9–12 months. This is why we invest heavily in pre-submission preparation — the cost of getting it right the first time is a fraction of the cost of a failed submission.
If you'd like to discuss your certification strategy before starting development, we offer free initial consultations as part of any new client engagement.