01What Counts as a Normal Outcome
A normal outcome is any result produced by a game operating correctly within its designed parameters. The following examples all constitute normal outcomes that are not eligible for dispute:
What Counts as a Normal Outcome
A normal outcome is any result produced by a game operating correctly within its designed parameters. The following examples all constitute normal outcomes that are not eligible for dispute:
Losing a bet due to the house edge
All casino games have a mathematical advantage for the house (expressed as the Return to Player percentage, or RTP). Over time, the house edge guarantees that the casino retains a percentage of all wagers. Losing money in games operating at their declared RTP is not a platform error — it is the expected outcome of gambling.
Extended losing streaks
Even in games with a low house edge (e.g., blackjack at ~0.5% with perfect strategy), statistical variance means players can experience losing streaks spanning hundreds or thousands of hands. This is mathematically expected and does not indicate a rigged or malfunctioning game.
Jackpot not hitting despite heavy play
Progressive jackpots and bonus features operate on random number generation with very low trigger probabilities. Playing a slot machine for extended periods without hitting the jackpot is entirely normal — the declared hit frequency applies over millions of spins, not individual sessions.
02Normal Outcome vs. Legitimate Dispute — Comparison
The following table distinguishes between outcomes the guarantee does not cover and situations that may qualify for a formal review.
Normal Outcome vs. Legitimate Dispute — Comparison
The following table distinguishes between outcomes the guarantee does not cover and situations that may qualify for a formal review.
Situation
Reviewable: Technical malfunction during play. Normal outcome: Normal game variance or loss.
RNG
Reviewable: Non-certified or tampered RNG suspected. Normal outcome: Certified RNG operating normally.
Payout
Reviewable: Declared win not paid by platform. Normal outcome: Loss from normal play, no payout due.
03When You DO Have Grounds to Escalate
While normal outcomes are excluded, the following situations related to game results may qualify for a formal dispute:
When You DO Have Grounds to Escalate
While normal outcomes are excluded, the following situations related to game results may qualify for a formal dispute:
Declared win not paid
If a game clearly displayed a winning result (e.g., a slot showed a winning combination, a hand was dealt a blackjack) but the platform did not credit the win, this is a platform failure — not a normal outcome. This qualifies for immediate escalation.
Game malfunction mid-bet
If the game froze, disconnected, or produced an error during an active bet, and the platform neither restored the bet nor credited the appropriate outcome, you have grounds to dispute. Most licensed platforms have a malfunction policy that provides a remedy — if they refuse to apply it, we can escalate.
RNG or fairness certificate concerns
If a game's RTP deviates significantly from its declared value over a statistically significant sample (typically 10,000+ rounds), or if the casino cannot produce a valid RNG certificate from an accredited testing lab (eCOGRA, iTech Labs, BMM Testlabs, GLI), this raises a legitimate fairness concern we can investigate.
04How GOOD CASINO Evaluates RNG & Malfunction Claims
When a player submits a claim involving a potential game malfunction or RNG concern, we apply the following independent verification process:
How GOOD CASINO Evaluates RNG & Malfunction Claims
When a player submits a claim involving a potential game malfunction or RNG concern, we apply the following independent verification process:
1. Session log request
We request the complete server-side session log for the disputed rounds, including bet amounts, outcomes, timestamps, and any error codes generated. This data is more reliable than client-side screenshots.
2. RNG certificate verification
We verify the casino holds a current RNG certificate from an accredited testing laboratory. Certificates must be renewed regularly and cover the specific game version in use at the time of the dispute.
3. Statistical analysis
For claims involving extended losing streaks or low RTP, we conduct a statistical analysis of the session data. Results more than 3 standard deviations from expected value over a sufficient sample warrant further investigation.
4. Platform malfunction policy review
We review the casino's declared malfunction policy (required under most licences). If a malfunction occurred and the platform failed to apply its own policy, this constitutes a platform failure regardless of the underlying game outcome.
05Understanding RTP and Variance
Many players file disputes based on misunderstanding how RTP and variance work. This section provides factual context to help players evaluate their own situations before filing.
Understanding RTP and Variance
Many players file disputes based on misunderstanding how RTP and variance work. This section provides factual context to help players evaluate their own situations before filing.
RTP is a long-run average
A slot machine with 96% RTP will return £96 for every £100 wagered — but only over millions of spins. In any individual session, outcomes can range from total loss to significant profit. Short-session results are dominated by variance, not by RTP.
Variance determines session swing
High-variance games (e.g., progressive jackpot slots) have rare but large wins and frequent small losses. Low-variance games (e.g., French roulette, baccarat) have smaller swings but the house edge still applies over time. Neither type indicates a malfunction during a losing session.
The gambler's fallacy
Each spin or hand is an independent event. A slot machine that has not paid a jackpot in 10,000 spins is not 'due' — the probability of hitting the jackpot on the next spin is identical to the first. Past outcomes do not influence future independent results.
06Responsible Gambling & When to Seek Help
If you are experiencing distress about gambling losses — regardless of whether those losses were due to a platform failure or normal outcomes — the following resources provide confidential support:
Responsible Gambling & When to Seek Help
If you are experiencing distress about gambling losses — regardless of whether those losses were due to a platform failure or normal outcomes — the following resources provide confidential support:
GamCare (UK)
Free, confidential information, advice, and support for anyone affected by problem gambling. gamcare.org.uk | 0808 8020 133
Gamblers Anonymous
International peer support network for people with gambling problems. gamblers-anonymous.org.uk
BeGambleAware
National gambling helpline and online support. begambleaware.org | 0808 8020 133
07How to File If You Believe It Was Not a Normal Outcome
If after reading this guide you still believe your loss was caused by a platform failure rather than a normal outcome, follow these steps:
How to File If You Believe It Was Not a Normal Outcome
If after reading this guide you still believe your loss was caused by a platform failure rather than a normal outcome, follow these steps:
1. Document the session
Take screenshots of the game screen showing the disputed round, your account balance before and after, and any error messages displayed. Download your session history from the casino's account section if available.
2. Contact the casino first
Submit a formal written complaint to the casino's support team describing the specific round, the expected outcome, and the actual outcome. Request the server-side session log for the disputed round.
3. Submit to GOOD CASINO
If the casino does not resolve the complaint within 7 days or disputes your version of events, submit the case to GOOD CASINO with all documentation. Be specific: round ID, timestamp, declared paytable, and actual outcome.
4. RNG/malfunction investigation
If a malfunction is suspected, we request the casino's RNG certificate and the server-side game log. This process typically takes 5–10 business days.
What Counts as a Normal Outcome
A normal outcome is any result produced by a game operating correctly within its designed parameters. The following examples all constitute normal outcomes that are not eligible for dispute:
Losing a bet due to the house edge
All casino games have a mathematical advantage for the house (expressed as the Return to Player percentage, or RTP). Over time, the house edge guarantees that the casino retains a percentage of all wagers. Losing money in games operating at their declared RTP is not a platform error — it is the expected outcome of gambling.
Extended losing streaks
Even in games with a low house edge (e.g., blackjack at ~0.5% with perfect strategy), statistical variance means players can experience losing streaks spanning hundreds or thousands of hands. This is mathematically expected and does not indicate a rigged or malfunctioning game.
Jackpot not hitting despite heavy play
Progressive jackpots and bonus features operate on random number generation with very low trigger probabilities. Playing a slot machine for extended periods without hitting the jackpot is entirely normal — the declared hit frequency applies over millions of spins, not individual sessions.
Misunderstanding game rules or paytables
A player who misunderstands how a game works — for example, not realising that a side bet has different odds, or misreading a paytable — cannot claim the outcome was unfair. It is the player's responsibility to understand the rules of any game they play. Casinos are required to make rules easily accessible, but are not liable for player misunderstanding.
Variance on short sessions
Short-session results (under 1,000 rounds for slots, under 500 hands for table games) can deviate significantly from theoretical RTP due to variance. A player winning or losing 30% above or below expected value in a short session is within normal statistical probability.
Normal Outcome vs. Legitimate Dispute — Comparison
The following table distinguishes between outcomes the guarantee does not cover and situations that may qualify for a formal review.
| Field | Platform Failure (Covered) | Normal Outcome (Not Covered) | Audit Method |
|---|---|---|---|
| Situation | Technical malfunction during play | Normal game variance or loss | Game logs + RNG certificate cross-check |
| RNG | Non-certified or tampered RNG suspected | Certified RNG operating normally | eCOGRA / iTech Labs RNG audit trail |
| Payout | Declared win not paid by platform | Loss from normal play, no payout due | Session log vs. declared paytable |
| Game freeze | Game froze mid-bet, losing bet not restored | Player closed browser voluntarily | Server-side session state records |
| Dispute basis | Platform acted outside declared rules | Player unhappy with outcome under correct rules | Rules documentation + session data comparison |
Scroll right to see all columns
When You DO Have Grounds to Escalate
While normal outcomes are excluded, the following situations related to game results may qualify for a formal dispute:
Declared win not paid
If a game clearly displayed a winning result (e.g., a slot showed a winning combination, a hand was dealt a blackjack) but the platform did not credit the win, this is a platform failure — not a normal outcome. This qualifies for immediate escalation.
Game malfunction mid-bet
If the game froze, disconnected, or produced an error during an active bet, and the platform neither restored the bet nor credited the appropriate outcome, you have grounds to dispute. Most licensed platforms have a malfunction policy that provides a remedy — if they refuse to apply it, we can escalate.
RNG or fairness certificate concerns
If a game's RTP deviates significantly from its declared value over a statistically significant sample (typically 10,000+ rounds), or if the casino cannot produce a valid RNG certificate from an accredited testing lab (eCOGRA, iTech Labs, BMM Testlabs, GLI), this raises a legitimate fairness concern we can investigate.
Paytable changed without notice
If the casino changed the game's paytable, RTP, or rules mid-session without notice, and you played on the old terms in good faith, you may have a legitimate claim for the difference in expected value.
How GOOD CASINO Evaluates RNG & Malfunction Claims
When a player submits a claim involving a potential game malfunction or RNG concern, we apply the following independent verification process:
Session log request
We request the complete server-side session log for the disputed rounds, including bet amounts, outcomes, timestamps, and any error codes generated. This data is more reliable than client-side screenshots.
RNG certificate verification
We verify the casino holds a current RNG certificate from an accredited testing laboratory. Certificates must be renewed regularly and cover the specific game version in use at the time of the dispute.
Statistical analysis
For claims involving extended losing streaks or low RTP, we conduct a statistical analysis of the session data. Results more than 3 standard deviations from expected value over a sufficient sample warrant further investigation.
Platform malfunction policy review
We review the casino's declared malfunction policy (required under most licences). If a malfunction occurred and the platform failed to apply its own policy, this constitutes a platform failure regardless of the underlying game outcome.
Determination
If no malfunction, RNG issue, or undeclared rule change is identified, the claim is closed as a normal outcome. If a platform failure is confirmed, we proceed with the standard guarantee enforcement process.
Understanding RTP and Variance
Many players file disputes based on misunderstanding how RTP and variance work. This section provides factual context to help players evaluate their own situations before filing.
RTP is a long-run average
A slot machine with 96% RTP will return £96 for every £100 wagered — but only over millions of spins. In any individual session, outcomes can range from total loss to significant profit. Short-session results are dominated by variance, not by RTP.
Variance determines session swing
High-variance games (e.g., progressive jackpot slots) have rare but large wins and frequent small losses. Low-variance games (e.g., French roulette, baccarat) have smaller swings but the house edge still applies over time. Neither type indicates a malfunction during a losing session.
The gambler's fallacy
Each spin or hand is an independent event. A slot machine that has not paid a jackpot in 10,000 spins is not 'due' — the probability of hitting the jackpot on the next spin is identical to the first. Past outcomes do not influence future independent results.
Before filing a dispute about a losing session, calculate how many rounds you played and compare your actual return to the declared RTP. If your actual return is within 2 standard deviations of expected, the outcome is statistically normal and unlikely to result in a successful claim.
Responsible Gambling & When to Seek Help
If you are experiencing distress about gambling losses — regardless of whether those losses were due to a platform failure or normal outcomes — the following resources provide confidential support:
GamCare (UK)
Free, confidential information, advice, and support for anyone affected by problem gambling. gamcare.org.uk | 0808 8020 133
Gamblers Anonymous
International peer support network for people with gambling problems. gamblers-anonymous.org.uk
BeGambleAware
National gambling helpline and online support. begambleaware.org | 0808 8020 133
Self-exclusion (GamStop UK)
UK players can self-exclude from all UKGC-licensed sites for 6 months, 1 year, or 5 years via gamstop.co.uk
All licensed casinos are required to offer self-exclusion and deposit limit tools. If you are struggling with gambling, use these tools before filing disputes — they are more effective at preventing further losses than any complaint process.
How to File If You Believe It Was Not a Normal Outcome
If after reading this guide you still believe your loss was caused by a platform failure rather than a normal outcome, follow these steps:
Document the session
Take screenshots of the game screen showing the disputed round, your account balance before and after, and any error messages displayed. Download your session history from the casino's account section if available.
Contact the casino first
Submit a formal written complaint to the casino's support team describing the specific round, the expected outcome, and the actual outcome. Request the server-side session log for the disputed round.
Submit to GOOD CASINO
If the casino does not resolve the complaint within 7 days or disputes your version of events, submit the case to GOOD CASINO with all documentation. Be specific: round ID, timestamp, declared paytable, and actual outcome.
RNG/malfunction investigation
If a malfunction is suspected, we request the casino's RNG certificate and the server-side game log. This process typically takes 5–10 business days.
ADR escalation if needed
If our review confirms a platform failure but the casino refuses to remedy it, we escalate to the licensing authority's ADR provider and issue a formal non-compliance notice.
Think Your Loss Was Caused by a Platform Failure?
If you believe a technical malfunction or undeclared rule change affected your result — not just bad luck — submit the case for independent review.
Not sure if your loss qualifies? Use our pre-check tool before filing a formal claim.