A frozen slot screen does not by itself mean a bet has vanished, and a missing animation does not prove the stake must be refunded. What matters is whether the operator accepted the gamble, whether an outcome was generated, and whether the game needs another decision from the player. In Great Britain, the Gambling Commission's RTS 10 interruption guidance says a result should stand if the operator received the gamble and the customer can no longer influence it. For a single-player, single-stage game interrupted before an outcome is generated, a deducted stake should be returned. A multi-stage game should instead be restored, as far as reasonably possible, to a state in which play can finish.
This guide explains those branches, the records needed to reconcile a round and what to ask when an account balance looks wrong. Great Britain's published standards are the regulatory anchor; GLI-19 section 4.16 is a separate testing standard, not a worldwide legal rule. The applicable licence, published game rules and facts of the individual round still matter. This is a systems and consumer-rights explainer, not advice that every operator or jurisdiction must use the same recovery outcome.
First separate the screen from the recorded round
An online casino round is not just what the browser displays. A player action travels from a device to a gaming platform or game server; the system records whether it accepted a wager, determines or continues an outcome, and posts the resulting account entries. The interface then shows that result. If the connection fails anywhere along this path, the player's last visible frame can be older than the authoritative transaction record. This explains why an apparently unspun reel may have a settled result in game history, or why a deducted amount may temporarily be held for a game that can be continued. It does not establish which event happened in a particular case without the record.
The technical distinction is explicit in GLI-19's interrupted-game definition: an interrupted game includes an unresolved outcome or an outcome that cannot properly be conveyed to the player. It lists communications loss, gaming-platform restart, player-device malfunction, abnormal player-software termination and a platform disable command as possible causes. Those are different failure modes with different recovery implications. Our remote gaming server explainer covers the game-hosting layer; the aggregation versus RGS guide shows why more than one technical party may appear in an incident trail. The customer-facing operator still needs to explain its treatment of the wager under its rules.
The basic question is therefore not simply “Did the screen freeze?” It is “What was the last recorded state of this specific round?” A screenshot documents the visible experience; the operator's game and account records establish acceptance, outcome generation, settlement and any later correction. Neither should be substituted for the other.
The four recovery paths
RTS 10A sets a fairness requirement for interruption policies and then gives distinct implementation guidance for gaming. The table below is a reading aid for that British guidance, not a promise that every casino game in every country resolves identically.
| Recorded position when play stops | British RTS 10 guidance | What to verify |
|---|---|---|
| Operator received the gamble; the player can no longer influence the result | The result should stand | Accepted round, generated result, settlement and account entry |
| Single-player, single-stage round; no outcome was generated | Any deducted stake should be returned | No generated outcome, reversal or credit entry |
| Stateful game with further decisions or stages | Take reasonable steps to restore the last known state and let the player finish | Saved choices, state, held funds and resumption route |
| Game with multiple participants | Treat fairly case by case | Game rules, timing, other players' state and final allocation |
The first row matters most for a typical one-action slot spin. If the accepted wager has already reached a point where the customer can do nothing more to change its result, losing the video feed does not necessarily unwind it. A prize or a loss may be reflected later in the account history. Conversely, the second row is about a genuinely undetermined single-stage round, not a round whose result exists but failed to render. An operator should not use the word “disconnect” as a blanket explanation for whichever settlement is most convenient.
The third row is different from a refund. A bonus feature, card choice or other game with stored decisions may need the prior state restored so the player can complete it. British RTS 10B requires recovery capability, including voiding where appropriate, and reasonable retention of pre-failure information. Its guidance mentions cards and hands, collected tokens, prize layouts, jackpot values and the state of bets as examples of information that may need restoration. These are examples, not a claim that every slot stores a deck of cards.
For multiplayer play, the timing and rules can affect other participants. RTS 10 does not supply a universal “refund everyone” formula: it calls for fair treatment case by case. In all four branches, RTS 5 adds the broader requirement to take reasonable steps to accept, process and settle gambles under the published operator and game rules, and to remedy faults that affect customers fairly.
Why money can appear missing before settlement
An interrupted, resumable round may have an amount committed to that game without a final win-or-loss entry. GLI-19 section 4.16.2 says that, for a system assessed against that technical standard, wagers associated with a game that can be continued are held until completion and player accounts reflect funds held in interrupted games. Its section 4.16.3 calls for a completion mechanism and for resolving that game before another instance of the same game. This is a laboratory benchmark, not an assertion that every real-world account labels pending funds in identical words.
Three amounts must not be confused: available account balance, money committed to an unfinished game, and the final result once the game is settled or voided. Depending on the product design, a display may show a debit immediately, later show a credit, or show the stake as held. A player cannot infer a permanent loss from one balance snapshot. Equally, an operator cannot establish a valid loss merely by pointing to an earlier debit while withholding the corresponding round result.
For British customers, RTS 1 requires current balance information to be displayed on relevant screens or easily accessible, and at least three months of account and gambling history to be available without contacting the licensee. At least 12 months must be available on request. The guidance says history should cover bets, results and winnings, and that players should have easy access to at least the last game's details even where a full detailed game history is not directly available. These are concrete starting points for a missing-stake query.
A practical reconciliation for one interrupted round
Consider an illustrative £2 single-stage slot round. The screen freezes just after the player presses play. There are three materially different explanations. If the server received the wager and generated the result, the £2 stake and any award should be reconciled to that result even if no animation appeared. If no outcome was generated and the £2 had been deducted, the British guidance points to returning it. If the event is actually a feature with a further player decision, the correct path may be to restore the feature rather than pay or refund it immediately. The £2 is an example only, not evidence about a commercial game.
To reconcile the round, a support or operations team should be able to identify the account and round, the accepted stake, the result status, a final or held-funds account entry, any reversal, and which published interruption policy governed that game. This is an editorial investigation checklist drawn from the standards, not a mandated UKGC field schema. Where an aggregator, game supplier and operator each maintain logs, matching their identifiers and timestamps avoids treating one front-end error as an entire transaction history. The iGaming payments infrastructure map discusses why movement between systems needs reconciliation rather than an assumption that all ledgers update simultaneously.
A retry deserves care. Reloading the game to retrieve an existing result is different from deliberately starting a new paid round. Before pressing play again, check whether the prior stake is still pending or whether the game offers a resume flow. That is a practical precaution, not a claim that a second click always duplicates the same transaction. If the player cannot see the status, ask support for the round identifier and final disposition in writing.
What recovery and game rules should disclose
British RTS 10C requires operators to make information about their interruption policies available to customers. Its guidance calls for common scenarios to be covered; it does not demand a script for every imaginable failure. A useful player-facing explanation should distinguish a completed outcome that was not displayed, an undetermined wager that is returned, a resumable feature and a voided game. It should tell the player where the final transaction can be found and how a problem can be raised.
The same transparency principle appears in RTS 5 result determination: accepted, processed and settled gambles should follow the published terms and specific game rules, and errors affecting customers should be corrected as soon as practicable. The Commission's guidance says customers should be notified when errors such as incorrectly settled bets have occurred. A general clause saying “malfunction voids all pays” should not be read in isolation from the actual applicable rules and fairness requirements.
GLI-19 provides a more detailed technical comparison. Its section 4.16.3 distinguishes games needing no further input from single-player games needing a restored decision point. For some multiplayer situations it specifies how a platform may act on behalf of a disconnected player under the rules while preserving results and not disadvantaging others. Those criteria help a reviewer ask precise questions, but GLI publication alone does not prove a particular British game was tested against GLI-19 or that another country's regulator adopted it.
When the result remains disputed
Start with the account history and the game rules in force at the time. Save a screenshot of the error and balances, but also note the date, time zone, game name, stake, any round ID, account transaction entries and messages from support. A screenshot is useful evidence of what the player saw; it is not a substitute for the operator's event record. Ask the operator to state whether the wager was accepted, whether an outcome was generated, whether the game was restored or voided, and how the balance entries map to that decision. Keep copies of the reply and relevant policy version.
If the explanation or settlement does not match the record, use the operator's formal complaints process. The Gambling Commission's player guidance expressly includes disputes over a win, payout, voided bet and IT issue. Its complaints procedure asks customers to give dates, times, amounts and evidence; the gambling business has eight weeks to resolve the complaint after receiving it. An unresolved eligible transaction dispute may then go to an approved ADR provider. The Commission itself does not decide individual gambling-transaction complaints. Our Great Britain gambling complaints and ADR guide explains the escalation boundary in detail.
For a progressive-jackpot round, the prize pool adds one more state to reconcile. RTS 10's gaming guidance says the jackpot value should be restored to its pre-failure state, and the published RTS 9 jackpot rules govern the wider award system. Our progressive-jackpot systems explainer covers that pool-level record. A frozen jackpot meter is not, by itself, evidence that an individual prize was won or lost.
What an operator should test before a failure happens
The useful test is not merely whether the page reloads. A recovery test should follow an accepted bet through a lost device connection, a delayed result display, a platform restart, an interrupted decision stage and any manual correction path. At each branch it should check that the same round is not settled twice, that a valid result is not silently discarded, that a refund is traceable and that the player can find the disposition in the account history. These are proposed audit questions, not a quotation from UKGC RTS 10 or proof that every supplier uses the same architecture.
RTS 10B supplies the regulatory reason: the system must recover from interruptions, void where appropriate and retain enough information to restore a pre-failure event. RTS 5 connects that design to testing and monitoring against published rules. GLI-19 gives a separate example of a structured test standard for held wagers and completion. Independent game testing is important, but a certificate is not a substitute for operational logs and a clear explanation of a particular incident.
Frequently asked questions
Does a casino disconnect automatically refund my stake?
No. Under British RTS 10 guidance, the result should stand when the operator has received the gamble and the player cannot influence the outcome. A deducted stake should be returned for a single-player, single-stage event interrupted before an outcome was generated. The round record and applicable rules determine which branch fits.
What if the reels froze before I saw the result?
The screen alone cannot show whether the outcome was generated. Check the game's round history and account entries, then ask the operator for the accepted wager, result status and settlement if they are unclear. An undisplayed result can still be a recorded result.
Can an unfinished bonus game be resumed?
British RTS 10 guidance says reasonable steps should be taken to restore stateful games to their last known state so the customer can finish. Whether a specific feature is resumable depends on its recorded state and rules; a stake refund is not the only possible outcome.
Why did my balance fall without a visible result?
The wager might be held for an unfinished game, settled with an outcome the device did not display, or awaiting correction. Those are possibilities, not a diagnosis. Review the game and account histories and request the operator's written reconciliation of the particular round.
What should I do if the operator and I disagree?
Preserve the timestamp, stake, game and round IDs, screenshots, account entries and correspondence. Raise a formal complaint with the operator and ask which rule and event record support its decision. For eligible British transaction disputes, ADR may be available after the operator process; the Commission does not adjudicate the individual wager.