How to Review a Reported Game Result Mismatch

A reported mismatch between an expected game result and the result shown on screen can be difficult to assess without a clear record of what occurred. Rather than relying on memory or assumptions, use a structured checklist to identify the relevant round, preserve available information and compare like with like.

This guide does not determine whether a result was correct. It outlines the details readers should verify before drawing a conclusion or submitting a support request.

1. Identify the exact round

Start by locating the specific game round in the available account or session history. Record any round identifier, game title and displayed status. If several rounds were played close together, check that the disputed entry has not been confused with the round immediately before or after it.

Where possible, note what appeared on screen without interpreting it. Separate direct observations—such as displayed symbols, cards, numbers or multipliers—from conclusions about what those elements should have produced.

2. Preserve the available evidence

Keep copies of information already available to you, such as the relevant history entry, an error message or the values shown by a verification interface. Avoid editing images or cropping out details that may help identify the round.

Create a short written sequence of events while the session is still fresh in your mind. Include only what you observed. Do not add an assumed cause, and do not treat a visual delay, animation or interface change as proof that the underlying result differed.

3. Compare the correct values

A meaningful comparison requires values from the same round and the same game mode. Check that every identifier matches before comparing an on-screen outcome with a history entry or verification record.

Review whether the game included optional features, multiple stages, bonus rounds, side selections or different payline settings. A value associated with one stage may not describe the final outcome of the entire round. Also distinguish between the initial result, any feature outcome and the final recorded settlement.

4. Check the game rules and paytable

Read the rules and paytable that apply to the game version you used. Verify the selected stake, active lines or ways, symbol requirements, multiplier rules and any conditions attached to special features.

Do not assume that similar-looking games calculate outcomes in the same way. Even within one title, different modes may use different rules. Confirm that your interpretation is based on the rules shown for the relevant version and configuration.

5. Review verification data carefully

If a game provides a result-verification process, copy each value exactly as displayed. Check for missing characters, extra spaces, capitalisation differences and confusion between similar characters. Confirm that the inputs belong to the disputed round rather than a later or earlier one.

Follow the stated verification sequence in the correct order. If the interface distinguishes between hidden, revealed or combined values, record each field under its proper label instead of rearranging them. A comparison is not useful when inputs from separate rounds or stages are mixed.

For a focused checklist relating to this issue, see reviewing a reported result mismatch.

6. Rule out display and session issues

Before concluding that two records conflict, refresh the relevant history page and compare the information again. Check whether the entry was marked as pending, incomplete, cancelled or otherwise unresolved when first viewed.

Note the device, browser or app environment used, along with any connection interruption or page reload. These details do not establish the cause of a mismatch, but they can help distinguish what was displayed locally from what appears in the recorded history.

7. Prepare a concise support request

If the discrepancy remains, organise the report so another person can reproduce the comparison. Include the round identifier, game title, observed outcome, recorded outcome, relevant verification values and the exact point at which the records appear to diverge.

Use neutral wording. Ask for clarification of the applicable rule or record rather than asserting misconduct without evidence. Do not send passwords, authentication codes, complete payment details or unrelated identity information.

Final checklist

Before submitting a report, confirm that:

• the round and game version are correctly identified;
• all compared records relate to the same round and stage;
• the applicable rules and paytable have been reviewed;
• verification values were copied exactly and entered in the stated order;
• screenshots or notes retain useful context;
• display or session issues have been considered; and
• the request explains the discrepancy clearly without including sensitive credentials.

A careful, round-specific record makes it easier to assess what differs, what remains uncertain and what information still needs clarification.