Spinbit problems: stuck withdrawals, failed logins and phone loading fixes

At 7am on the bus you tap Spinbit and the balance screen freezes halfway through loading, or at 11pm a withdrawal that should have moved sits on pending. In most cases the cause is simple: a session that has gone stale, a browser holding old data, or a check on the account that has not finished yet.

A withdrawal that stays pending longer than expected

The player sees the withdrawal listed as pending while the balance is already reduced, and nothing changes for a long stretch.

• A verification step on the account is still open and holding the payout.
• Bonus credit is still tied to the balance, so part of the funds cannot leave yet.
• The payout details do not match the name registered on the account.
• A recent password or email change has placed the account under a short security review.
• The request was submitted twice, and the second one is blocking the first.

1. Open the withdrawal history and confirm the request is shown as pending rather than cancelled.
2. Check the account section for any open verification request attached to the payout.
3. Upload the missing document in the format the request asks for.
4. Look at whether bonus funds are still active on the balance.
5. Clear any remaining bonus requirement by playing the games it applies to.
6. Compare the payout details with the name on the account and correct anything that differs.
7. Remove a duplicate request before it confuses the queue.
8. Sign out and back in so the history refreshes.
9. Switch from the phone browser to a desktop browser and check again.
10. Give the security review time to clear after a password change.
11. Keep a screenshot of the pending entry in case you need to raise it.
12. Make no further withdrawals while the first one is unresolved.
13. Write to support with the request reference if the entry stays pending after the review window.

Contact support once the account shows no open verification and the entry still has not moved.

Login refused or account locked after failed attempts

The player types the password, sees an error, tries again, and then the message changes to a lock notice.

• The password is mistyped, often through autocorrect or a trailing space.
• The email address used at signup is different from the one typed.
• Too many failed attempts have triggered a temporary lock.
• Two-factor codes are arriving late or to an old phone number.
• A password change was started but not completed.

1. Type the password into a notes field first to see exactly what is being entered.
2. Remove any space at the start or end of the password.
3. Confirm the email address matches the one used at registration.
4. Turn off autocorrect on the phone keyboard before trying again.
5. Wait out the temporary lock instead of retrying, since each attempt restarts it.
6. Use the password recovery route to set a fresh password.
7. Choose a password that you have not used on other services.
8. Check that two-factor codes reach the current phone number.
9. Complete any half-finished password change before signing in.
10. Try a different browser if the login page returns an error before the form submits.
11. Sign in from a private window to rule out old saved data.
12. Contact support if the lock notice remains after the recovery email has been used.

Write to support when the recovery route fails and no new password has been set.

Phone browser shows a blank page or games that will not load

The player opens the site on a phone and gets a white screen, a spinning loader, or a game that stops after the first frame.

• The browser cache holds an old version of the page.
• The mobile connection has dropped to a weak signal.
• An ad blocker or privacy extension is blocking game scripts.
• Too many tabs are open and the phone has run short of memory.
• The browser itself is out of date.

1. Close every tab that is not needed and reload the page.
2. Switch from mobile data to Wi-Fi, or the other way round, to test the connection.
3. Clear the browser cache and cookies for the site.
4. Reload the page and sign in again after clearing.
5. Disable ad blockers and privacy extensions for the site.
6. Update the phone browser to the current version.
7. Restart the phone to free up memory.
8. Open one game at a time rather than several in separate tabs.
9. Try a second browser to see whether the fault follows the browser.
10. Turn off any battery-saving mode that suspends background scripts.
11. Test the site on a different network to rule out a local block.
12. Keep the phone screen on while a game loads, since a sleeping screen can cut the session.
13. Contact support if the same game fails in two browsers on two networks.

Reach out when other players on a different network load the site without trouble and your phone still does not.

Identity checks stuck or documents turned down

The player uploads a document and the status stays on review, or the file comes back marked as rejected with no clear reason.

• A photo is blurred, cropped or catching a glare on the surface.
• The document has expired or the corner covering the expiry date is missing.
• The name or address on the document differs from the account details.
• The file type or size is outside what the upload form accepts.
• Only one side of a two-sided document has been sent.

1. Take the photo on a plain surface in daylight rather than under a lamp.
2. Fit the whole document inside the frame, with all four corners visible.
3. Check that the expiry date shows and that the document is still valid.
4. Send both sides when the document has two.
5. Match the name on the document to the name on the account exactly.
6. Use the file type the upload form accepts.
7. Reduce the file size if the upload keeps failing.
8. For proof of address, use a document that shows your name and full address.
9. Upload the replacement file only once, then wait for the review to move.
10. Delete the old rejected file from the upload area so it is not reviewed again.
11. Keep the original documents on the phone in case a second copy is requested.
12. Players who still cannot reach the upload form can open Spinbit through https://spinbit1.co.nz/ and try again from the account area there.
13. Repeat the upload from a desktop browser if the phone camera makes the image unclear.

Contact support when a valid document has been rejected twice without a stated reason.

Quick Reference

These are the checks that resolve most cases, matched to what the player sees first.

A pending payout is usually waiting on something the player can finish themselves, most often a document. A login failure is more often a typing problem than a system fault, so retyping beats repeated attempts. Locked accounts clear faster when the player stops trying and uses recovery. A blank phone page follows the browser, so a second browser tells you where the fault sits. Rejected documents usually fail on image quality rather than on content. The first check in each row costs little and removes the most common cause before support gets involved.

Keeping the registered name, address and payout details identical across the account prevents most of these problems before they start.