Casino Disconnection: Verify Round Status Before Replaying

Why this matters

For Gambling Commission-licensed gambling in Great Britain, a frozen screen alone proves neither that a bet failed nor that it settled. Match the round to its transaction records before replaying; interruption rules depend on the game and timing.

Screen Freeze Limitations

A frozen display does not identify the cause of an interruption. The problem may concern the device, connection or operator systems. A round could already have been accepted or settled while the screen stopped updating. Do not interpret a spinning icon or an error message as confirmation that the bet was cancelled.

Stop repeated clicks and retain the visible error with its time and time zone. Ask for the round record rather than relying on a screenshot alone. Account history, the receipt and the operator's explanation should agree about acceptance and settlement. A screenshot can support a dispute, but it does not establish what happened on the server.

GB RTS10 Scenarios

The Gambling Commission's RTS 10 gaming guidance distinguishes several situations. When the operator has received the gamble and the player has no further influence on the outcome, the result should stand. For a single-participant, single-stage game interrupted before the outcome is generated, any stake already deducted should be returned. These conditions matter; neither rule promises every disconnected player a refund.

For stateful multi-stage games, the guidance calls for reasonable steps to restore the last known state. Multiple-participant games need a fair resolution appropriate to the circumstances. These rules concern operators licensed by the Gambling Commission in Great Britain, meaning England, Scotland and Wales. They should not be presented as the law for every country or every game format.

Transaction Trail Reconciliation

Match the round ID, game and provider to the time, stake, debit and any credit in account history. A change in the overall balance could include other transactions, and an unchanged balance alone does not confirm that no bet was received. Look for a matching record and ask about any missing or pending entries.

Request the operator's receipt, outcome and settlement trail for that specific round. Keep copies before the history becomes harder to locate. If two records conflict, state exactly which fields disagree and ask for reconciliation. Avoid placing another bet or depositing money to test whether the first round failed. A second transaction cannot resolve the first record.

Policy Escalation Path

Read the operator's interruption policy for the relevant game and ask which provision it applied to your round. The policy should explain common interruption scenarios, but a generic answer may not establish the status of your particular transaction. Ask for the factual sequence: whether the gamble was received, whether an outcome was generated and how the stake was settled.

If the records remain disputed, follow the operator's formal complaints procedure and save evidence of receipt. After eight weeks unresolved, or an earlier final position or deadlock, ask its named ADR provider about eligibility. This free, independent route does not guarantee acceptance or repayment. Our complaint evidence guide explains what to keep and when to refer.

Practical checklist

• Stop duplicate clicks immediately to prevent multiple bets.
• Check account balance history for a debit entry.
• Save round ID, timestamp, and stake amount.
• Contact support for a receipt and settlement trail.
• Review the operator's interruption policy before escalating.