You tap the Spinbit login button and the page throws you back with an error, or your account shows as locked with no clear reason. The most common cause is a run of failed password attempts that triggered a temporary lock on the account.
Account locked or login failing
Players see a red error under the username field, a message that the account is locked, or a button that does nothing after a correct password. spinbit-nz.co.nz applies a lock after several wrong attempts, so the fix starts with regaining access rather than retyping the password faster.
- Wrong password typed more than once, often from muscle memory
- Caps Lock or an autocorrect change in the password field
- Saved credentials in the browser that no longer match
- Account locked automatically after repeated failed attempts
- Email or username entered instead of the login name
- Stop entering the password at the first error; each wrong try extends the lock.
- Clear the password field completely and type the password by hand.
- Check Caps Lock and the keyboard layout before you submit again.
- Use the password reset link on the login page to set a fresh password.
- Open the reset email in the same browser you will use for the site.
- Pick a new password that differs clearly from the old one.
- Remove the saved login from the browser and let it store the new one.
- Turn off any virtual private network that changes your location.
- Try the login page in a private browsing window to rule out old cookies.
- Log in on one device only and close other sessions of the site.
Contact support with a screenshot of the error and your registered email if the lock does not lift after a reset.
Pages and games failing on a phone
On a phone the lobby may stay on a blank screen, spin forever, or open a game that loads halfway and freezes. The usual cause is a weak mobile connection combined with an outdated cached version of the site in the browser.
- Mobile data or Wi-Fi signal dropping during loading
- Browser cache holding an old copy of the page
- Scripts blocked by an extension or security app
- Outdated version of the phone browser
- Too many tabs open and memory running low
- Switch between Wi-Fi and mobile data to see which one loads the page.
- Close every other tab before you open the site again.
- Clear the browser cache and stored data for the site only.
- Reload the page with a hard refresh if your browser allows it.
- Update the phone browser to the latest version available.
- Turn off content blockers for the site and reload.
- Open a game in portrait first, then rotate the phone to landscape.
- Disable any battery saver that limits background browser activity.
- Try a different browser on the same phone to compare behaviour.
- Restart the phone if games still freeze after all of the above.
Contact support with the phone model, browser name and a screenshot if only this site fails while other pages load normally.
Identity checks stuck or documents refused
Players submit their documents and wait, then see the status unchanged or a rejection notice without a clear reason. The most common trigger is a photo that is blurred, cropped or missing a corner of the document.
- Photo taken at an angle or with glare on the surface
- Edges of the document cut off by the camera frame
- Details that do not match the name on the account
- Expired document uploaded by mistake
- A second page or the back of a card not included
- Send both sides of every document, even when only one side seems needed.
- Place the document on a flat, dark surface with no glare.
- Fit the whole document inside the frame with all four corners visible.
- Keep the text sharp and readable at normal size without zoom.
- Use the original file from your photo gallery, not a screenshot.
- Match the name on the document to the name on the account exactly.
- Replace any document that has passed its expiry date first.
- Upload one document at a time and wait for each status to change.
- Resubmit with the corrected file if a rejection lists a clear reason.
Contact support if the status does not move after a corrected upload, or if a rejection gives no reason you can act on.
Withdrawal still pending
The balance shows the request as pending while the amount has already left your available balance. The usual cause is a verification step that has not finished, which holds the request in the queue.
- Identity checks still open on the account
- Bonus funds included in the withdrawal request
- Payment details that do not match the account holder
- More than one request submitted in a short window
- A request cancelled earlier and sent again
- Check that your identity status shows as complete, not pending.
- Cancel any duplicate request so only one is active.
- Make sure the payment details carry the same name as the account.
- Separate bonus funds from cash before you request a withdrawal.
- Confirm the bonus conditions attached to any funds you played with.
- Leave the request alone once it is pending; editing can reset it.
- Keep the account logged out while the request is under review.
- Note the status shown on the request before you contact anyone.
- Resubmit only after the first request reaches a final status.
- Write to support with the request reference if the status stays unchanged.
Contact support with the request reference and your identity status if the request has not moved and no reason is shown.
Quick Reference
The table below pairs each problem with the cause that explains most cases and the first check to run.
| Problem | Usual cause | First check |
|---|---|---|
| Login fails or account locks | Repeated wrong password attempts | Reset the password once, then log in by hand |
| Phone pages or games freeze | Stale browser cache on a weak connection | Clear site data and switch network |
| Identity check stuck | Blurred or cropped document photo | Re-upload with all corners in frame |
| Withdrawal pending | Verification not yet complete | Confirm identity status is complete |
| Bonus related hold | Bonus funds mixed with cash | Split bonus and cash before requesting |
Each check in the table costs a minute and removes the most likely cause before a support ticket is needed. A login lock almost always clears after one clean reset and a single careful attempt. Blank phone screens usually come from cached data, so clearing it is faster than reinstalling anything. Document checks fail on photo quality far more often than on the document itself. Pending withdrawals rarely sit because of the payment side; an open identity check is the usual reason. A Spinbit bonus can keep funds in play longer, so players who request a withdrawal too early see the request held rather than paid.
Before you start a session, log in once with the password typed by hand, finish identity checks early and keep bonus funds separate from cash; that routine removes most locks, loading stalls and pending withdrawals before they start.