You closed the login page before it finished and the site now says your account is locked. That lockout usually comes from too many failed sign-in attempts in quick succession.
Failed sign-in attempts and a locked account
Players usually see a message that the password is wrong or that the account is temporarily locked.
- A mistyped password or a keyboard layout that changes characters.
- Saved login details that no longer match after a password change.
- Several attempts in a row that trigger the protection lock.
- A broken browser session that keeps resending old data.
- An email address entered with a space or a different spelling.
- Close every tab that has the login page open and open a fresh one.
- Type your email address slowly and check for spaces at the beginning or end.
- Re-enter the password by hand instead of using a saved entry.
- If the password field shows dots immediately, clear the field and type again.
- Wait for the lock period to end before your next attempt, because each new try extends it.
- Use the password reset flow if you truly cannot recall the password and the lock keeps returning.
- Open the reset link in the same browser you use for normal sign-in.
- Set a new password that differs from the one you used before.
- Sign out of the site on any other device where the account stays open.
- Save the new password only after you confirm the sign-in works.
- If the reset email does not arrive, check the spam folder and the exact address you registered.
- Turn off a password manager extension briefly if it fills the field with old data.
- Try the phone browser instead of a desktop tab to rule out a stored session problem.
- Contact support after the lock continues past the period stated on screen and the reset still fails.
- Send a screenshot of the lock message so the team can trace the attempts.
Contact support when the reset link works but the account stays locked or when the site shows an error rather than a wrong password.
Deposits and withdrawals rejected by limits
The player sees a rejection notice at the cashier step, often without an explanation of which limit was hit.
- The amount falls below or above the range allowed for the chosen method.
- Repeated deposits within a short window reach a personal or method cap.
- The payout request exceeds the balance allowed for a single withdrawal.
- The account still waits for a pending withdrawal, which blocks a new request.
- An unfinished identity check holds the payout while deposits still pass.
- Note the exact wording of the rejection and the amount you entered.
- Change the amount to a different value and submit again, keeping well inside the usual range.
- Try the other direction if the notice mentions a minimum: a small deposit may settle the check.
- Split a large payout into smaller requests only if the cashier offers that option.
- Clear any earlier withdrawal that is still waiting, because a second request can be declined.
- Return to the deposit page and confirm which methods are available to your account.
- Switch to another method shown in your cashier when the first one keeps declining.
- Complete any identity step the account shows as open before sending more payout requests.
- Keep a record of each declined attempt with its amount and time.
- Repeat the step once, then pause, because rapid retries can raise a flag on the account.
- Use the phone browser if the cashier page does not update after a rejection.
- Check that a bonus requirement is not forcing the amount into a restricted range.
- Contact support when the same amount declines twice with no clear reason.
- Include the method, the amount and the notice text in your message.
- Contact support when limits block a payout you need and the cashier offers no smaller option.
Contact support when the same limit blocks the request after several tries and the cashier shows no reason.
A deposit missing from the Spinbet balance
The bank shows the payment as completed while the casino page keeps the old balance.
Most delays come from a step between the payment provider and the casino account. www.au-spinbet.com processes the deposit on its side and then updates the balance, so a lag at that hand-off leaves the money in neither place on screen.
- The payment provider has not yet confirmed the transfer to the casino.
- The page was refreshed before the confirmation arrived.
- The deposit went to an old payment reference that no longer matches the account.
- A bonus selection on the deposit form delayed the credit.
- A browser session lost part of the request after the bank approved it.
- Keep the bank confirmation open in a second tab as proof of the payment.
- Do not close the cashier page while a status message shows progress.
- Wait for the status to change before pressing refresh or repeat deposit.
- Refresh the balance once after the status message disappears.
- Sign out and back in to force a fresh balance from the server.
- Open the transaction history and look for the deposit entry.
- Compare the reference on the bank receipt with the reference in the history.
- If the history shows the deposit, the balance is likely behind a page cache; clear the browser data.
- If the history lacks the deposit, avoid sending a second payment at once.
- Try the transaction history again in the phone browser on the same connection.
- Send support the bank receipt, the payment reference and the time of the attempt.
- Mention any bonus you selected on the form.
- Respond to support questions about the payment reference in the same thread.
- Check the balance again after support confirms the credit.
- Contact support when the bank payment is real, the history never shows it, and the balance stays unchanged.
Withdrawals pending longer than expected
The payout request shows as pending while the balance stays reserved and the player cannot use it.
- The identity or address check is still open on the account.
- Bonus play has not yet reached the point where a payout can leave.
- The request sits behind a queue during busy hours.
- A change of payment method since the last deposit needs a manual review.
- Several requests were sent at once and only one moves.
- Open the account section and check which identity steps remain open.
- Finish any open step before sending more messages about the payout.
- Look at the transaction history to confirm the request is recorded, not lost.
- Cancel and resubmit only if the cashier allows it and the request is clearly stuck.
- Do not send a second payout request while the first is pending.
- Use the same payment method for the payout as for your last deposit.
- Clear the browser cache if the status never updates.
- Sign in through the phone browser to see whether the status differs.
- Wait for the review to finish before asking for a new estimate, as repeated questions slow the queue.
- Keep the request reference for your message.
- Contact support when the payout stays pending past the period stated on the cashier page and the identity steps are all complete.
- Describe the payment method and the request reference in one short message.
- Avoid opening duplicate tickets about the same payout.
- Reply to support rather than starting a second thread.
- Check the transaction history once more after support responds.
Contact support when the endpoint states the payout is on hold and the identity steps are closed.
Use one browser and one saved password for every session, and send each deposit or payout request only after the previous one finishes.
