Fairness, RNG audits, GLI, and eCOGRA
Fairness is not one certificate. A random-number test, accurate paytable, comparable tournament input, secure transaction ledger, and fair dispute process address different risks.
What an RNG review can cover
Section titled “What an RNG review can cover”A laboratory can evaluate random-number generation, statistical behavior, source-code controls, game math, or implementation against a named standard. The report scope matters. A certificate for one operator, server, or release does not automatically cover every game bearing the same brand.
GLI’s published standards include GLI-15 for Electronic Bingo and Keno Systems and GLI-19 for Interactive Gaming Systems. A published standard describes technical requirements; it is not evidence that a particular app passed testing. The jurisdiction and the certificate’s stated system determine which requirements apply.
The GLI Certified mark guidance explains its certification program. eCOGRA’s eGAP seal page distinguishes operator, software and affiliate seals. Match the exact seal and its scope to the claim being made; do not treat those categories as interchangeable.
Certificate checklist
Section titled “Certificate checklist”Open the evidence and record:
- testing or certification organization;
- operator and domain;
- game, platform, or system covered;
- certificate or report identifier;
- standard and test scope;
- issue and expiration dates, if provided;
- status through the issuer’s verification link or official contact, where available;
- whether the named software version matches the current product.
A logo image with no link or identifier does not let you verify the claim. A laboratory may not offer a public search for every report. If a report cannot be checked online, use the laboratory’s own contact details to ask whether it can confirm the identifier and scope. Do not send account passwords or identity documents to a contact supplied only by the app’s badge.
Worked example: a report with limited coverage
Section titled “Worked example: a report with limited coverage”This is an original hypothetical example, not a certificate issued to a real operator. Suppose a report names “Example Game A, RNG module 1.2,” while the installed app identifies its RNG module as 1.3.
| Claim or question | What the example evidence establishes | What is still needed |
|---|---|---|
| RNG module 1.2 passed the named tests | The report’s stated result for that module and scope, if the issuer confirms it | The actual test scope and any conditions or limitations |
| The current module 1.3 is covered | The version numbers differ; the old report alone does not establish coverage | A current report or issuer confirmation that explicitly covers 1.3 |
| Withdrawals will be paid | An RNG-only report does not test this promise | Payment terms, transaction records and the relevant complaint route |
| Opponent matching is fair | An RNG-only report does not establish matchmaking behavior | Matching and settlement rules, plus evidence covering their implementation |
A newer date on a marketing page does not resolve the version gap. The relevant question is whether the issuer confirms coverage of the software actually used.
Regulation is separate
Section titled “Regulation is separate”A US state regulator can approve an operator and game for its market, require technical controls, and receive complaints. That is stronger evidence of market authorization than a generic lab badge, but it still does not guarantee player profit or eliminate normal variance.
Confirm the domain through the relevant regulator. Do not apply a New Jersey approval to play from a different state.
Skill tournaments need different evidence
Section titled “Skill tournaments need different evidence”Randomness may produce the initial card or call sequence, while player decisions produce the score. An RNG test alone does not show that opponents received comparable material or that matchmaking was neutral.
Review:
- score formula and penalties;
- game-material assignment;
- opponent matching and settlement;
- tie, disconnect, and unmatched-entry rules;
- anti-collusion and automation controls;
- game history and dispute evidence.
Room bingo checks
Section titled “Room bingo checks”For room-style bingo, inspect card construction, call history, claim validation, prize division, and progressive rules. A fair draw does not repair an undisclosed prize split or incorrect card claim.
Claims to avoid
Section titled “Claims to avoid”Do not write “certified safe” from a testing logo, “provably fair” without a reproducible method, or “rigged” from a losing streak. State the narrow evidence available and what remains untested.
When reporting an anomaly, preserve the game ID, rules, timestamps, call sequence, card, score breakdown, transaction, device version, and support case. Specific records are more useful than a screen recording of only the result.