A deposit that leaves the bank but never lands in the balance is the symptom most players miss, because the bank app already shows the money gone. In most cases the transfer is still sitting with the payment provider, not lost, and no second attempt is needed yet.
Money sent from the bank but missing from the balance
The player sees a completed transfer in the banking app and an unchanged casino balance. Several causes are common:
- The payment provider still holds the transfer in a pending state.
- The transfer was sent to a reference or account that does not match the player profile.
- The bank marked the payment for a manual review before releasing it.
- The deposit was made in a session that timed out before the casino recorded it.
- The money went to an old or secondary account that is not the one in use.
Work through these steps in order:
- Open the transaction history on the account and note the status of the payment.
- Compare the reference on the bank statement with the reference shown in the history.
- Leave the payment alone rather than sending it again while it shows as pending.
- Check whether the deposit was made while the page was reloading or the connection dropped.
- Make sure the name on the bank account matches the name on the player profile.
- Confirm the payment was sent from an account the player owns, not a shared or third-party one.
- Take a screenshot of the bank record and of the transaction history for later reference.
- Ask the bank whether any review or hold is attached to the transfer.
- Keep watching the transaction history, because a pending payment may still settle on its own.
- Contact support with both records if the balance stays unchanged after the payment clears.
Contact support once the payment has fully cleared at the bank and the balance still shows nothing, or as soon as two payments appear for a single deposit.
Login refused or account locked after failed attempts
The player types the password and sees a refusal, then a locked message after several tries. The usual culprits are:
- The password was mistyped, often with a trailing space or the wrong letter case.
- Repeated failures triggered a temporary lock.
- The username is wrong, for example a phone number instead of the registered email.
- A password manager fills in an outdated saved password.
- Two-factor codes arrive after their short validity window has passed.
These steps resolve most of these cases:
- Stop retrying at once, because each failure extends the lock.
- Type the password by hand into a plain text field to check for stray spaces.
- Switch off autofill and enter the credentials manually.
- Confirm the exact email or username used at registration.
- Check the keyboard language and caps lock before trying again.
- Wait for the lock period shown on screen to pass.
- If a two-factor code is required, request a fresh one and enter it promptly.
- Use the password reset route if the password is genuinely forgotten.
- Open a private browser window to rule out saved data causing the refusal.
- Contact support if the login still fails after the lock expires and the reset was completed.
Contact support when a reset was completed, the lock has expired and the spinbit login still refuses the correct password.
Site or games that stall on a phone browser
The player taps a game on the phone and sees a blank screen, a frozen spinner or a game that closes mid-round. Typical causes:
- The mobile connection is weak or switches between networks mid-session.
- Old browser cache or cookies hold a stale version of the site.
- Too many open tabs consume the phone’s memory.
- A browser extension or ad blocker interrupts scripts the games depend on.
- An outdated phone browser cannot run the game format.
Try these fixes in sequence:
- Reload the page once to see whether the game recovers.
- Switch from mobile data to Wi-Fi or the other way round.
- Close every other tab and app running in the background.
- Clear the browser cache and cookies for the site.
- Disable ad blockers and any script blockers for this page.
- Open the site in a private window to test without extensions.
- Update the phone browser to its newest version.
- Restart the phone and reopen the browser.
- Try a different browser on the same phone to isolate the fault.
- Contact support if one game stalls while every other game loads normally on the same phone.
Contact support when the whole site fails in every browser and on a stable connection, or when a single game keeps failing after the cache is cleared.
Deposits or withdrawals declined by limits
The player submits a payment and sees a decline message tied to a limit rather than to insufficient funds. Why it happens:
- The amount falls below or above the range accepted for that payment route.
- The player’s own account limits, set earlier, cap the payment.
- A recent deposit is still settling, so the withdrawal amount is not yet available.
- The chosen route has a cap lower than the amount requested.
- Remaining playthrough conditions tied to a bonus hold part of the balance.
These steps put the account back in order:
- Read the decline message in full, because it names the limit that was hit.
- Check the account limits set in the player profile.
- Split the amount across permitted payments if the route allows it.
- Wait for any earlier deposit to settle before requesting a withdrawal.
- Review whether an active bonus ties up part of the balance.
- Choose a different payment route when the first one has a lower cap.
- Keep a record of each declined attempt with the date and amount.
- Use spinbit-nz.co.nz to reach the account area and confirm which payment options suit the player’s country.
- Contact support when the same amount is declined on every route and no limit explains why.
Contact support if the decline continues after the limits are checked and a different route was tried.
Quick Reference
Use this table to match the symptom on screen to the first thing worth checking.
| Problem | Usual cause | First check |
|---|---|---|
| Deposit missing from balance | Payment still pending with the provider | Transaction history status |
| Login refused | Typo or autofill of an old password | Type the password by hand |
| Account locked | Repeated failed attempts | Wait out the lock period |
| Game stalls on phone | Stale cache or a weak connection | Clear cache and switch network |
| Payment declined | Route or account limit reached | Account limits in the profile |
Each row points to the check that rules out the most likely cause first, so start there instead of trying everything at once. A pending deposit needs patience, not a repeat payment. A lock needs a pause, because more attempts only extend it. Phone faults shrink quickly once the cache and network are dealt with. Declined payments usually point to a limit that can be seen in the profile or in the decline message itself. The table is a starting point, not a verdict, so move to the section above when the first check does not settle the issue. Records of each attempt make every support request faster to resolve.
Keep one habit that prevents most of these problems: note each deposit, login and payment attempt with the date and amount in a single place, and use the same name and payment account across the bank and the spinbit casino login. A clear trail proves what happened when something goes wrong.
