Reconstruct a live-casino round from the history, not the replay

Start with the round you are trying to identify

A live-dealer picture and an account entry answer different questions. The picture shows what reached the screen; the account entry records financial activity attributed to the customer. To investigate an unclear completed round, match the game and round reference to its accepted stake, result and return.

A replay without that match cannot establish the customer's settlement.

This is a method for reading records after a streaming problem, not a measured test of network delay. No live account, private history or studio log was accessed. The worked record below is invented and labelled as such.

It gives a reader a repeatable way to identify what is known and what still needs an operator's explanation.

Great Britain's Gambling Commission addresses customer history in RTS 1, transaction information in RTS 2 and interrupted gambling in RTS 10. These are distinct requirements. Their existence does not prove that an individual transaction was correct, nor does it give a customer access to every internal server event.

Sources: RTS 1 – Customer account information; RTS 2 – Displaying transactions; RTS 10 – Interrupted gambling.

Know what the published history requirement promises

RTS 1B requires easy access to at least three months of account and gambling history without contacting the licensee, and at least twelve months on request. Its gaming guidance allows full or summarised information and distinguishes details of the last game from summaries of earlier activity.

It should not be paraphrased as a promise that every old live round has a customer-visible video replay.

That limit matters when a statement contains a total for a session rather than each decision. A summary can help reconcile money without showing why a particular action was accepted or rejected. Conversely, a detailed round view may explain one game while omitting unrelated transfers that affected the overall balance.

Before comparing two screens, record their scope. Is one showing the latest hand, a session, a calendar day or an account period? Note the currency, time zone and filter if displayed.

If a field is not supplied, mark it absent. A worksheet with a visible gap is more reliable than one completed with a guessed timestamp or a familiar interpretation of an unlabeled total.

Sources: RTS 1 – Customer account information.

Build a record with enough identifiers to match

Start a private note with the operator, provider and exact table or game name, to the extent those are visible. Add the date, approximate local time with time zone, and any round or transaction reference the interface supplies. Do not invent a reference because the support form appears to expect one.

An explicitly missing identifier is useful information.

Keep three observations separate: the action attempted, any acceptance message actually seen, and the later history entry. A click is evidence of an attempted action. An acceptance message adds information, but its absence during a frozen stream does not by itself prove acceptance or rejection.

The history and operator's records are needed to connect that attempt to a settlement.

Describe a frozen picture literally. For example, write that the image stopped updating while a round reference remained visible, if that is what happened. Do not translate that into the server stopped, the dealer stopped or the bet was cancelled.

Those conclusions require evidence from another part of the system. Precise observation keeps a record useful without claiming technical access the reader does not have.

Sources: RTS 2 – Displaying transactions.

A fictional ledger with a real reconciliation method

The following is a constructed example in pounds. It assumes the history reports gross returns separately from stakes, and that there are no deposits, withdrawals, transfers or other rounds within the interval. R-A, R-B and R-C are invented references.

No game's payout rules are being inferred from them.

The total stake is £14 and total gross return is £14. Closing balance is therefore £50 + £14 − £14 = £50. The £8 credit on R-A does not mean £8 profit; that round's stake was £4.

R-C has a credit without a net gain.

If the stream froze during R-B, the ledger would still show a £4 deduction and no return for that reference. That establishes what this fictional record contains. It does not establish that the deduction was correctly settled, what action was available, or why the stream froze.

Those are separate questions for the exact round evidence.

Reconcile the right quantity before alleging a mismatch

An account balance, session net position and gross return are different quantities. RTS 2E concerns the session's net position; the fictional table instead displays both individual movements and a running balance. The arithmetic is consistent only because the example explicitly excludes other movement.

A real balance comparison may need those additional entries.

Take a further fictional variation: the final account balance reads £55 instead of £50, and a separate £5 transfer into the product appears in the same interval. Including that transfer reconciles the balance; treating the extra £5 as round profit would not. This does not imply transfers are always the explanation.

It shows why the scope of the record must be settled first.

Similarly, determine whether a field named return includes the stake, and whether winnings is a profit field or a gross credit. Do not subtract stakes twice. Where labels are unclear, preserve the label exactly in the private note and ask for its definition.

A discrepancy stated as opening balance plus credits minus debits differs from closing balance by a specified amount is more precise than a general claim that a displayed win went missing.

Sources: RTS 2 – Displaying transactions.

Read interruption policy against the recorded stage

RTS 10 distinguishes several interruption circumstances. Its guidance says an accepted gamble can stand when the customer has no further influence on the outcome; it also addresses pre-outcome interruption of a single-participant single-stage event and restoration of stateful games. Those distinctions prevent a blanket conclusion that loss of video means a refund.

Use the record to identify the unresolved stage, not to choose the most favourable branch automatically. If acceptance is uncertain, ask whether the gamble was received. If a further decision was due, ask which state was retained and what the game's interruption policy specified.

If settlement exists, request the result and the basis for applying that policy to the identified round.

This article does not reproduce blackjack, roulette or baccarat rules. It also does not assign a default action to every live table. A public help article may combine several products in a short answer; a specific round still needs its own game and policy.

The recorded observation and the applicable rule should meet at the same reference, rather than being connected solely because both mention a disconnection.

Sources: RTS 10 – Interrupted gambling.

Make a support question that can be answered

A useful request could say: please confirm the accepted stake, recorded result, gross return and interruption treatment for the identified round; the picture froze at the approximate time recorded in my note. This is a suggested question, not a message sent during our research. It names the missing fields without claiming a diagnosis of the provider's systems.

Keep the relevant record private. There is no need to publish a full account statement to explain a single round. If preparing an excerpt for a public discussion, remove personal details and unrelated financial entries.

Retain the original privately so that editing the excerpt does not become the only surviving record.

Distinguish a support answer from independent verification. An operator explanation is evidence of its stated treatment. It may resolve the arithmetic, leave a rule question open or identify a correction; those are different outcomes.

The worksheet has space for each rather than a single fixed verdict. This note makes no claim about response times, refunds, compensation or the result of a complaint. None of those was tested.

Sources: RTS 1 – Customer account information; RTS 10 – Interrupted gambling.

State the conclusion at the level the evidence permits

The most useful conclusion can be modest: these entries reconcile to the closing balance, but the interruption rule for this round remains unexplained. Another could be that the public summary lacks the individual record required to resolve the issue. Neither finding establishes fraud, an audit failure or a measured latency figure.

The original diagram beside this article connects identifiers, transactions and policy through a single round record. Its arrows describe a reading method, not a measured data path or timing diagram. A screenshot of the video may help describe what was visible, but it cannot replace the accepted-stake record.

Equally, a balanced ledger does not prove every game action was correct.

The documentary sources were checked on 19 September 2026. No live incident was manufactured, no wager was made and no private account information was collected. The exercise can be completed after stopping play.

Further gambling is not a useful way to recreate a missing record or establish what happened in an earlier round. Gambling can cause harm.