A live casino glitch: what happens to your bet and how to collect evidence
If a live casino freezes, do not place the bet again and do not reload the page over and over. First check the game history and the balance: the bet may have been accepted before the video dropped and the result may already be determined on the server. In another case the round may not have started at all, and the amount debited should come back under the operator's rules.
There is no single answer that “all bets are void in a malfunction”. In regulated systems the moment of interruption matters. If the operator has already received the bet and the player could no longer influence the outcome, the result usually stands. If the outcome had not yet been generated in a single-stage game, the bet may be returned. In a multi-stage game the system may restore the last state. Record the round ID, the time, the amount and the error message, then ask for a decision in writing.
The video froze, but the game may have continued
A live casino consists of several layers: the studio stream, the betting interface, the game server, the wallet and the user's connection. A frozen picture does not prove the server stopped.
A roulette bet, for example, may have been accepted before the betting window closed. After that the video feed disappeared, but the wheel kept spinning and the result went into the log. A completed round will appear in the history. Placing the bet again because of a blank screen creates a new transaction and complicates the dispute.
Look not only at the stream but at the status in the Game History: accepted, pending, settled, void or a similar term.
How the moment of the failure affects the fate of a bet
The UKGC RTS 10 approach separates several situations. It applies to British licensees, but it gives a useful model for checking on other markets too. The rules of your licence and your operator may differ.
| Moment of interruptionPossible statusWhat to check | ||
| Before the bet was confirmed | The bet may not have been accepted | Whether there is an ID and a debit |
| After acceptance, once the player's input is over | The result may stand | The log and the outcome of the round |
| Before the outcome was generated in a simple game | The bet may be returned | A void or refund status |
| In a multi-stage game | The state may be restored | Whether the same round can be continued |
| The failure affected several players | The decision follows a procedure | The interruptions policy |
The word “may” is essential here. Without the log you cannot tell at which stage the operation stopped.
Which failures occur in a live casino
Most often a player sees one of six scenarios:
- the video stream froze or disappeared;
- the bet button gave no clear confirmation;
- the amount was debited but no round appeared;
- the result on the table did not match the entry in the history;
- the game restarted in the middle of a hand;
- the balance updated with a delay.
Each scenario needs a different set of evidence. A screenshot of a blank screen is useful, but without the time and the ID it does not show which transaction the failure related to.
First steps: a five-minute protocol
- Stop placing new bets.
- Take a screenshot of the error, the table, the balance and the time.
- Open the game history in a new tab, if you can do it without closing the disputed screen.
- Note the game name, the provider, the table number and the dealer, if visible.
- Copy the round and transaction IDs.
- Check whether the balance changed a few minutes later.
- Write to support and ask them to register a ticket.
Do not clear the cache or reinstall the app before the data is recorded. Such actions can remove local information, although the server log stays with the operator.
What not to do after a disconnection
Do not open the same table on several devices and do not try to repeat the action to test the error. Do not top up the balance for a “control round”. New transactions create additional IDs and can get mixed up with the disputed one.
Do not accept a bonus or compensation in chat until you know whether it closes an official claim. Sometimes a goodwill gesture is unrelated to any admission of error, and sometimes the terms of the offer include a waiver of further claims. Ask for the terms in writing.
Do not publish screenshots with your name, email, account number or payment details in an open channel. A complaint needs the full original, but it should be sent to the operator, the ADR, the regulator or an authorised helper through a secure channel.
How to tell a local problem from an operator's failure
Check your connection, but do not try to prove the outcome yourself. Switching between Wi-Fi and mobile data can show that the problem is local. Yet even a local drop does not answer the question of whether the server accepted the bet.
Save:
- the device model and the app version;
- the browser and the operating system;
- the type of connection;
- the approximate start and end time of the failure;
- whether the same problem appears in another section of the site.
You do not need to send the operator passwords, two-factor codes or a full bank card number.
What to ask support for
The phrase “please check” is too general. State the facts and ask questions that can be answered with a document.
An example message:
On 3 August at 21:14 my local time, in the game [name], table [number], a bet of [amount] was debited. After confirmation the stream froze. Transaction ID [number]. Please state the status of the bet, the outcome of the round, the time the server accepted it and the clause of the interrupted game policy under which it was settled.
Also ask for a ticket number and a copy of the answer by email.
Which evidence carries the most weight
A strong timeline links one event to one transaction. It contains the exact time with the time zone, the amount, the balance before and after, the round ID, the entry in the history and the correspondence.
If a screen recording was already running, keep the original file. Do not edit it. But do not postpone your complaint in order to reproduce the error again with real bets.
| EvidenceWhy it is neededCommon mistake | ||
| Round ID | Finds the event in the log | Only the game name is saved |
| Time and time zone | Matches the server records | Writing “in the evening” |
| Balance before and after | Shows the movement of funds | The starting value is missing |
| Screenshot of the history | Records the status | The transaction number is cropped out |
| Ticket number | Confirms the complaint | Communication only in a disappearing chat |
If the history and the screen show different things
Do not conclude that the result was substituted on the basis of a single stream frame. Video lag, a display of the previous round or an interface error are all possible. Ask the operator to match the game log with the table ID and the time.
If the dispute concerns a card game, clarify whether the last state was restored. For roulette or a simple bet, ask whether the outcome was generated before the interruption. The answer should explain the logic of the settlement, not just report the result.
When to move from chat to a formal complaint
Move to the formal procedure if support does not state the status of the transaction, different employees give contradictory answers, the amount has not returned within the stated period or the history was changed without explanation.
In the complaint, state the remedy you want: provide the log, restore the unfinished round, return the bet or explain the settlement. Do not demand both “return my bet and pay my win” if the facts do not support both.
After the operator's answer, check which regulator and which ADR mechanism apply to your account and your GEO. Not every regulator handles individual money disputes directly.
How IPU.bet helps
IPU.bet does not run a casino's game server and cannot determine in advance the outcome of a disputed round. Through the rating you can choose operators and then check their licence and their Interrupted Games policy.
In a dispute you can send IPU.bet support the timeline, the round ID, the screenshots and the operator's answers. The team will help organise the materials and identify the next available channel. The outcome and a refund are not guaranteed.
What to remember
A stream failure and a failure of the game transaction are not the same thing. The main question is whether the bet was accepted and whether the outcome had already been determined.
Do not repeat the bet. Save the ID, the time, the balance and the history. Ask for a written decision citing the interruption policy. The more precise the timeline, the less the dispute depends on the words “everything froze for me”.
Before playing, check the operator in the IPU.bet rating and find its rules on technical failures. If a dispute has already arisen, stop betting and send support the full evidence package for an initial review, with no promise of a result.
FAQ
Is the bet returned if the live casino froze?
Not always. It depends on the moment of the failure, the status of the bet, the type of game, the operator's rules and the applicable regulation.
What matters more: a screenshot or the round ID?
Save both. The ID helps find the server record, while the screenshot captures what the player saw.
Can I reload the page?
Capture the screen and the ID first. A reload can then help restore the interface, but it does not change a bet the server has already accepted.
What if the bet is missing from the history but the money was debited?
Save the balance and the payment record, do not bet again and ask them to search for the transaction by the exact time and amount.
Is a frozen video proof that the result is wrong?
No. The video and the game log can update with different delays. The specific round has to be checked.
