Quick answer: a frozen screen, disconnect, error message or “rollback” label is an observation, not proof of the round’s final result. Pause before reopening the game or creating another round. Save the exact message, time zone, round or session reference, balance, game history and wallet history. Then classify the state as unresolved, resumable, completed, voided/refunded or rolled back only when the records and the applicable rule support that description.
Use this order: preserve the screen and timeline, check game history separately from transaction history, compare the two records, and ask a verified support route one focused question. This guide explains evidence handling; it does not promise a resume, refund, void, rollback, payout or particular SuperAce88 result.
Start with the state you can actually see
An interruption can happen on a phone, browser or network while a round is loading, after an action is accepted, or while the result animation is being displayed. Those moments look similar to a reader but can map to different server records. A reconnect screen can mean that a state is still available. A missing animation can coexist with a completed transaction. A “rollback” word may describe a displayed instruction rather than a completed account adjustment.
External frameworks illustrate why the distinction matters. The UK Gambling Commission’s RTS 10 discusses fair treatment during interruptions, restoration of state for multi-stage games and the possibility of voiding a gamble in the cited UK framework. GLI-19 is an industry technical standard that describes records and recovery controls. Neither document proves how a particular Philippine website, provider or game behaves. An operator help page, such as bet365’s broken-games article, is also an example of that operator’s route, not a universal rule.
| Observed state | Game-history record | Wallet or transaction record | What you may conclude | Next safe action |
|---|---|---|---|---|
| Error, freeze or disconnect | Unknown, loading or absent | Unknown | Interruption observed; outcome unresolved. | Save the message, timestamp, game name and current balance before retrying. |
| Reconnect or resume prompt | Round or session reference exists | Stake or hold may be pending | A resumable state is possible, not guaranteed. | Use the documented resume route once; do not open a second round. |
| Result visible in history | Result, round ID and time recorded | Matching debit/credit or adjustment | Records support a completed entry, subject to the controlling rule. | Save both histories and compare IDs, amounts and time zone. |
| Void or refund label | Round marked void, cancelled or returned | Reversal or credit recorded | A record supports that label; it is not a general promise of a refund. | Capture the rule wording and the ledger entry; ask only about any mismatch. |
| Rollback or correction label | Original and later status visible | Adjustment, reversal or replacement entry | A correction is recorded; the reason and timing still need evidence. | Keep the first and latest snapshots and identify which entry superseded the other. |
Preserve a timeline before taking another action
Write down the local date, clock time and time zone shown by the device or account. Add the game title exactly as displayed, the round or session ID if present, the action immediately before the interruption, and the visible balance before and after. If a notification or error text appears, capture it without editing the screenshot. A short note such as “screen froze after the wager button; no result animation; balance changed from the amount shown” is more useful than “the game stole money.” It distinguishes observation from conclusion.
Do not clear app data, reinstall, switch accounts, place another wager or repeatedly refresh before this first record is saved. A second action can create a new session and make the original event harder to isolate. If the game offers one clearly identified resume control, note the time and result of that action. If it asks for a password or one-time code through an unexpected message, stop and navigate independently to the known official support route.
Check game history and wallet history as separate records
Game history answers “what does the round record say?” Wallet or transaction history answers “what account movement was posted?” They may use different IDs, posting times or statuses. A completed game record without a matching wallet line is an unresolved reconciliation issue. A wallet adjustment without a visible round may be a delayed or hidden record, but it is not proof of fraud or a duplicate charge.
Compare the exact round or transaction ID, amount, currency label, status, timestamp and time zone. If the interface shows a session ID but no round ID, preserve the session ID and the navigation path used to find it. If it shows a balance change but no history entry, record the balance and time rather than guessing which round caused it.
| Evidence item | Capture timing | Redact before sharing | Support value |
|---|---|---|---|
| Error or reconnect screen | Immediately after interruption | Username, email, device identifiers, QR codes and notifications unrelated to the case | Shows the observed client state and exact wording. |
| Game-history row | After the history page loads | Other rounds, personal profile fields and unrelated balances | Connects the game label, round/session ID, result and timestamp. |
| Wallet or transaction row | Same time window, with time zone | Full payment credentials, account numbers and unrelated transactions | Shows debit, credit, reversal, status and transaction reference. |
| Applicable rule or help page | At the time you check the record | Nothing sensitive; preserve URL and capture time | Identifies the clause that support should apply, without assuming it is universal. |
| Short support question | After the packet is complete | Passwords, OTPs, recovery phrases and unnecessary identity data | Requests a precise explanation instead of a conclusion or accusation. |
Describe the issue without overclaiming
Use neutral language: “At 14:03 PHT the screen showed an error after the action; game history is pending; wallet history shows one debit; please identify the applicable round status and rule.” Avoid declaring that a round is definitely lost, refunded or rolled back until a record supports that label. Terms can also differ: a void may cancel an event, a refund may describe a returned stake, and a rollback may describe a reversal to an earlier state. Use the exact label shown and ask what record produced it.
For a verified escalation, the existing casino support and transaction-record guide helps organise a case file. If a message asks for credentials or sends a new login link, review the account-security and phishing guide first. These links describe evidence and safety steps; they do not establish a particular game result.
What this checklist cannot establish
- It cannot establish that SuperAce88, a provider or a game uses any particular rollback, resume, void or refund procedure.
- It cannot turn an external regulator or laboratory standard into a SuperAce88 rule, licence statement or fairness guarantee.
- It cannot prove a duplicate debit, fraud, liability, payout or recovery outcome from a screenshot or arithmetic alone.
- It does not recommend another wager, chasing losses, increasing stakes or creating more activity to “test” a frozen round.
- It does not ask for or require passwords, one-time codes, recovery phrases or full payment credentials.
Frequently asked questions
Does a frozen screen mean the round failed?
No. It proves that an interruption was visible on the device. Check game history and wallet history separately before describing the outcome.
Should I reopen the same game immediately?
First save the message, time, round reference and balance. If the site presents a documented resume control, record what happens. Do not open a new round or repeatedly refresh while the original state is unclear.
What is the difference between void, refund and rollback?
The labels can have different meanings in different rule sets. A void may cancel a round, a refund may describe a returned amount, and a rollback may describe a reversal to an earlier record. Use the exact status and ask which rule and ledger entry created it.
What if the wallet changed but game history did not?
Keep both records and mark the pair as unmatched. Note IDs, amounts, timestamps and time zones, then ask verified support to identify the corresponding round or adjustment. Do not label it fraud or a duplicate charge without more evidence.
Which screenshots are safe to share?
Share only the minimum screenshots needed for the case: the error, relevant history rows and the rule URL. Mask passwords, OTPs, recovery phrases, full card or account numbers, QR codes and unrelated personal data before using a verified route.
Sources and editorial disclosure
- UK Gambling Commission RTS 10 — Interrupted gambling — UK framework example for fair interruption handling and restoration capability.
- Gaming Laboratories International GLI-19 v3.0 — industry technical standard, not evidence of any SuperAce88 implementation.
- bet365 Help Centre — Broken Games — operator-specific example only.
Source note: the pages above were checked on 10 August 2026. UK Gambling Commission material is UK-specific; GLI-19 is a technical standard; bet365 is an operator example. None establishes SuperAce88 game providers, interruption policy, result source, licence, wallet architecture or payout outcome. Examples are educational and should be checked against the current authenticated account record and applicable terms.
