A spinning wheel that never stops, or an error message on a deposit form, is the moment most players notice something is wrong at the site. In most cases the cause is a browser or connection glitch, or a mismatch between the request and the account conditions in place.
Games that stall or fail on a phone browser
The page loads but the reels freeze, the sound disappears or a game refuses to open at all, which usually points to a browser or network fault rather than the game itself.
- The phone browser is out of date or an old tab is holding cached content.
- The connection drops or switches between mobile data and Wi-Fi mid-session.
- Several game windows are open at once and the phone is short on memory.
- A background download or another open site is using most of the bandwidth.
- A browser extension or private mode blocks scripts the games need.
- Close every other tab and window so the game has the phone’s full attention.
- Refresh the page once, then wait for the reels to finish loading before tapping anything.
- Update the phone browser to the latest version it offers, then reopen the site.
- Clear the browser cache and stored site data, which removes stale files from older sessions.
- Turn off private browsing for this session, since it can block the storage the games rely on.
- Switch off any ad-blocking or script-blocking extension, then refresh again.
- Move to a stable Wi-Fi network instead of mobile data if the signal is weak.
- Restart the phone to free up memory before opening another game.
- Open one game at a time rather than several in separate tabs.
- Test a single game on its own; if it loads, the fault was local to the other titles.
- Try a different browser on the same phone to see whether the problem follows the browser.
- Disable any battery-saving mode that limits background activity while the game runs.
- Check that the phone’s operating system is updated, then retry the game.
- Note the exact wording of any error message and which game produced it.
Contact support if the same game fails on a second browser and a stable network, or if the error names a server fault rather than your device.
Deposits and withdrawals refused because of limits
The payment screen returns a message that the amount falls outside the limit for the account or the method, so the transaction never moves forward.
- The figure typed is under the minimum or over the maximum allowed for that payment route.
- The method has a daily or monthly ceiling that the player has already reached.
- The amount is below the minimum a withdrawal may leave, or above a single payout ceiling.
- The method chosen for the payout differs from the one used to deposit.
- The account has a temporary restriction placed on payments while a review runs.
- Retype the amount carefully; a misplaced digit is the most frequent reason for a refusal.
- Compare the figure with the limit shown for the chosen payment method on the payment page.
- Split a large withdrawal into smaller requests only if the rules for the account allow it.
- Use a method that matches the way the money came in, which most operators require for payouts.
- Wait out any daily ceiling and resubmit the request after it resets.
- Change to another payment route where the limits suit the amount you want to move.
- Complete any outstanding identity step, because payments can pause until it is done.
- Remove pending requests that are holding part of the available balance.
- Check the account status area for a note about a payment restriction.
- Retry once after a short break, in case the refusal was a temporary system issue.
- Keep the reference code from the failed attempt so support can trace it.
- At Australian online pokies, https://australian-onlinepokies.org/ sets its own ceilings per payment method, and the payment page shows the figure that applies to your account before you confirm anything.
- Contact support if a correctly sized request is refused while no restriction appears on the account.
Reach out to support when the payment page shows no limit that explains the refusal, or when a method that worked before now rejects a normal amount.
Identity checks that stall or reject documents
The verification screen stays on pending for a long stretch, or a submitted document comes back marked as unreadable or expired.
- Photos are blurred, cropped or taken in low light so the text cannot be read.
- The document shown has passed its expiry date.
- The name or address on the document differs from what is on the account.
- Only one side of a two-sided document was sent.
- A file format or size that the upload field does not accept was used.
- Place the document flat on a plain surface and photograph it in bright, even light.
- Capture all four corners and the full text, with no glare across the printed area.
- Send every side of a document that has information on both faces.
- Use a document that is still valid on the day of the upload.
- Match the spelling of the name to the account exactly, without nicknames or initials.
- Save the image in a common file format the upload field accepts.
- Shrink a large photo before sending so the upload does not time out.
- Upload each document once; repeated copies slow the review rather than speed it up.
- Add a short note with the upload if a name change explains the difference.
- Reopen the verification area after a day to see whether the status moved.
- Replace a rejected document with a clearer copy rather than resending the same file.
- Make sure the address on the proof of address is the one currently on the account.
- Send the replacement from the same device and connection as the original.
Contact support when a clear, valid document is rejected twice without a stated reason, or when the pending status does not change.
Withdrawals sitting pending for longer than expected
The payout shows as pending in the account history, the balance is reduced, and the money has still not arrived.
- An identity check is still waiting, which holds every payout behind it.
- A bonus is attached to the balance, and the play conditions tied to it are not yet met.
- The request was submitted on a non-working day, so the review queue is longer.
- The payout method details are wrong or point to a closed account.
- Several requests were queued at once, and each is handled in turn.
- Open the account history and confirm the request status rather than relying on memory.
- Finish any outstanding identity step, since payouts wait on it.
- Check whether a bonus is linked to the balance and whether its play conditions are met.
- Confirm that the payout details are correct and belong to you.
- Cancel duplicate requests so only one legitimate payout is in the queue.
- Allow for weekends and public holidays, when review queues move more slowly.
- Keep the reference number shown in the history for any later question.
- Make sure the account email inbox is reachable in case a query is sent.
- Avoid starting a new request while an earlier one is still open.
- Note the date the request was submitted, which support will ask for.
- Check that no deposit is still clearing, because a payout can wait behind it.
- Reopen the history after a reasonable wait to see whether the status changed.
- Contact support if the status has not moved and no query has reached you.
Contact support when the payout stays pending with no visible reason and no message arrives asking for anything further.
Finishing identity verification early, before the first payout request, clears most of these problems before they start.