Phone browser problems: games and pages that will not load

• Weak or unstable mobile data or Wi-Fi.
• An outdated phone browser that cannot run the game scripts.
• Too many open tabs and background apps using memory.
• A VPN or ad blocker cutting off part of the page.
• Cached page data from an earlier visit clashing with the current version.

1. Switch between Wi-Fi and mobile data to see whether the connection is the cause.
2. Move to a spot with a stronger signal before loading a game again.
3. Close unused tabs and background apps to free memory on the phone.
4. Update the phone browser to its current version.
5. Turn off the VPN and any ad blocker for the session, then reload.
6. Clear the browser cache and cookies for the site.
7. Open the site in a private browsing window as a clean test.
8. Restart the phone and load one game at a time.

Deposits that leave the bank but never reach the balance

• The payment provider has taken the money but not yet confirmed it to the casino.
• A reference or account detail was entered in a way the payment could not match.
• The bank placed the transaction on hold for its own checks.
• A failed page load at the final step of the payment.
• The deposit went to an account other than the one used forhttps://www.spinbit1.co.nz/ .

1. Refresh the balance and the deposit history before doing anything else.
2. Keep the bank confirmation in a screenshot or a note with the reference.
3. Compare the account details used for the deposit with the profile details on Spinbit.
4. Wait for the payment provider to finish its own confirmation of the transfer.
5. Check that the payment screen was not closed before the confirmation message.
6. Make no second deposit until the first one is located.
7. Gather the transaction reference and the amount from the bank statement.
8. Send that reference to support through the contact route on the site.

Withdrawals still pending after the expected wait

• Account checks that must be finished before any payout is released.
• An unfinished deposit that the payout depends on.
• The payout details on the profile not matching the player’s own name.
• A request made during a busy period for the payout team.
• A bonus or play condition still attached to part of the balance.

1. Open the withdrawal history and note the exact status shown.
2. Complete any identity or address step that the account still lists as open.
3. Make sure the payout details carry the same name as the account profile.
4. Check that the deposit behind the withdrawal has fully settled.
5. Avoid sending a second request while the first is pending.
6. Finish any remaining play condition before expecting the payout.
7. Note the reference of the withdrawal for later messages.
8. Contact support if the status has not moved after the stated wait for the method.

Deposits and withdrawals declined by limits

• The amount sits above the per-transaction cap for that payment method.
• The amount sits below the minimum the method accepts.
• The account still has a lower limit because checks are not finished.
• The chosen method does not support the payout amount requested.
• A repeated pattern of payments triggered a routine account review.

1. Note the exact wording of the decline message before closing it.
2. Reduce or raise the amount to sit inside the range the message describes.
3. Choose a payment method that accepts the amount you want to move.
4. Finish any account step that keeps a lower limit in place.
5. Space out payments instead of sending several close together.
6. Try a smaller test amount first to confirm the method works.
7. Keep a note of the declined attempt and its reference.
8. Contact support if a correct amount is still refused.

Quick Reference