On the bus to work you open the site and the lobby stays half drawn, or on a quiet Sunday evening the wallet page returns an error instead of your balance. Most of the time the cause is something on the player's side: a weak connection, an old browser, a document that does not match the registered name, or a mistyped password used too many times.

Games and pages that will not load on a phone

The screen shows a spinning loader, a blank field where the game should be, or a button that does nothing when tapped.

• A mobile connection that drops or switches between Wi-Fi and mobile data mid-session.
• An outdated phone browser that no longer handles the scripts a live lobby needs.
• Leftover cache and cookies holding a broken copy of the page.
• Several tabs or background apps competing for memory.
• A temporary fault on the game provider's side rather than on your device.

1. Close every other tab and app, then reload the page once from the address bar.
2. Switch off Wi-Fi and use mobile data, or the reverse, to see whether the connection is the cause.
3. Open the lobby on a second device to compare results.
4. Clear the browser cache and cookies for the site only, which keeps other logins intact.
5. Update the phone browser to its current version through the store you normally use.
6. Restart the phone, since memory pressure is a common cause of frozen game windows.
7. Turn off any content blocker, ad filter or private relay for the site.
8. Try one simple table game first; if it opens while a live game does not, the issue sits with that single game.
9. Disable battery saver, which often pauses scripts in the background.
10. Note the game name and the exact message, as this speeds up any investigation.
11. Repeat the same steps on the second device to confirm the pattern.

Contact support when the lobby opens on one device but the same game fails on every device and connection you try.

Payments refused because of limit rules

The wallet screen shows a deposit or withdrawal refused, with a note pointing to a limit rather than to your balance.

• Your account has a personal limit lower than the amount you entered.
• The amount falls below or above the range the method allows.
• An unfinished identity check blocks part of the wallet until it is cleared.
• An open bonus carries its own cap on withdrawals while it is active.
• Two requests were submitted close together and the second clashed with the first.

1. Open your account limits in the profile and compare them with the amount you entered.
2. Change the amount to fit inside the range shown, then resubmit.
3. Use a different payment option from the wallet list if the current one has a narrow range.
4. Wait for the first request to finish before sending a second one.
5. Check whether a bonus is still active, since its rules can cap the withdrawal.
6. Finish any pending identity step, because the wallet can stay partly closed until then.
7. Enter the amount without spaces or symbols, matching the currency shown.
8. Keep the confirmation reference for every request you send.
9. Retry once after a fresh login rather than from a page left open for hours.
10. Compare a deposit and a withdrawal of the same size to see which side is blocked.
11. Write down the exact error text before contacting anyone.

Reach support when the amount fits every rule you can see and the payment is still refused.

Identity checks stuck or documents turned down

The verification page sits on pending, or a document comes back marked as rejected without a clear reason.

• A photo with glare, blur or a cropped edge that hides a corner.
• Details that differ between the document and the registered account.
• A document that has expired or is close to expiring.
• An accepted file type or size not respected.
• A selfie that does not clearly show the same face as the ID.

1. Photograph each document on a flat surface in daylight, with all four corners visible.
2. Match the name, spelling and date of birth exactly to the account details.
3. Send the current version of the document, not an old copy.
4. Upload in the format and size the form accepts, and avoid screenshots of scans.
5. Send both sides of a two-sided document.
6. For a selfie, look straight at the camera and keep your whole face in the frame.
7. Submit one document set at a time so the reviewer sees a clean file.
8. If a document was rejected, replace it rather than resending the same file.
9. Keep the notification you receive, as it names the step that failed.
10. Wait for the review to close before uploading a second version of the same document.
11. In the message to support, list the document type and the rejection text.

Contact support when every document is clear and current but the status never moves past pending.

Sign-in failures and an account locked after attempts

The login form returns an error, then locks the account after several tries, even though you are sure the password is right.

• A small typo in the password, made worse by autocorrect or a slipped keyboard layout.
• An old password saved in the browser or a password manager.
• A username entered as an email, or the reverse.
• Too many failed attempts in a row, which triggers the lock on purpose.
• A leftover session still open on another device.

1. Type the password by hand in a plain field to rule out autocorrect.
2. Check that the keyboard language matches the characters you need.
3. Remove the saved credential from the browser and enter it fresh each time.
4. Confirm which identifier the form expects, username or email address.
5. Stop trying once the lock message appears, because more attempts extend it.
6. Wait for the lock to lift on its own, then sign in once with the correct details.
7. Use the password reset on https://spinbit-aus.com/ to set a new password, then sign in from a single device.
8. Log out of every other device before the next attempt.
9. Turn off any tool that fills the form automatically.
10. Keep the error text from the login screen for reference.
11. Send support the time of the failed attempt and the exact message shown.

Contact support when the lock does not lift after the stated wait or the reset link never reaches your inbox.

Quick Reference

The table pairs each symptom with the cause seen most often and the first check worth doing.

A page that freezes is almost always local: the browser, the phone or the connection. Payment refusals that mention limits come from the rules attached to the method or to the account itself. Verification problems follow document quality more often than anything else. A lock after several failures is a safety feature, not a lost account. One clean sign-in per device after the lock lifts settles most cases. The same habit of keeping documents fresh and passwords unique prevents a repeat of every entry in the table.

Keep one current photo of your ID and a recent proof of address saved in your files, with the name spelled exactly as on the account, and most of these interruptions never return.