“Why does my Unibet login keep saying the account is locked?” Most players who see that message typed the wrong password a few times in a row, and the site now blocks further tries on purpose. The same kind of small mismatch between what the player expects and what the account shows explains most payment and loading faults too.
Locked out after too many failed sign-in tries
The player types the right password and still lands on a locked-account screen or a red error message.
- The password was mistyped several times, so the lock kicked in automatically.
- The wrong part of the email address is capitalised or contains a space.
- The saved password in the phone browser is out of date.
- Another person on the same device left a session open.
- A password reset was started but never finished.
- Stop retrying at once, because every extra attempt restarts the lock timer.
- Type the email address by hand instead of pasting it, checking for hidden spaces.
- Clear the saved password for the site in the phone browser, then enter it fresh.
- Finish any password reset email you requested earlier, even an old one.
- Close every browser tab on the site, reopen one tab and sign in again.
- Switch off any password manager autofill for this one page and type the credentials manually.
Contact support once the lock survives a fresh password and a cleared browser, since only they can lift it.
A deposit left the bank but the balance shows nothing
The bank statement shows money gone, while the casino balance and transaction history stay unchanged.
- The payment is still moving between the bank and the casino.
- The deposit was sent to a different account than the one now open.
- The deposit was declined at the casino end and is on its way back.
- A bonus code was attached to a payment that did not qualify for it.
- The player checked the wrong currency or a second account.
- Take a screenshot of the bank entry with the date and reference number visible.
- Open the transaction history on the account and note whether the deposit appears as pending.
- Confirm you are signed in to the same account you used for the deposit.
- Wait for the payment to settle before assuming it is lost, since bank transfers can lag.
- Repeat the check after signing out and back in, because the balance sometimes refreshes late.
- Gather the screenshot, the reference number and the account email in one message.
- Send that message to support and keep the bank’s own reference on file until the case closes.
Contact support as soon as the bank marks the payment as completed and the balance still shows nothing.
Phone browser loads the site or games badly
Pages stall, game windows stay black, or buttons do nothing when the site is opened on a phone.
- An old cached copy of the page is being served from the browser.
- The connection dropped or switched between wifi and mobile data mid-load.
- A browser add-on or content blocker is stopping part of the page.
- The phone is low on memory after many open tabs.
- The browser itself is an outdated version.
- Close all tabs, reopen the browser and load the page once more.
- Clear the browser cache and cookies for the site only, so saved logins elsewhere stay intact.
- Turn off content blockers or private browsing for this page and reload.
- Switch to a stable connection and avoid moving between wifi and mobile data during a game.
- Update the phone browser through its normal update route, then restart the phone.
- Try a second browser on the same phone to see whether the fault follows the browser.
Contact support when every browser on the phone fails while another device loads the site normally.
A withdrawal stays pending longer than expected
The request sits in a pending state and the money never reaches the player’s chosen destination.
- Identity checks on the account are still open.
- A bonus attached to the account has play conditions that are not met yet.
- The payout details differ from the ones used for earlier deposits.
- Several withdrawal requests are queued at the same time.
- The payment provider on the receiving side is holding the transfer.
- Open the account profile and finish any identity step marked as outstanding.
- Check whether an active bonus still carries play conditions before the money can leave.
- Cancel duplicate requests and keep a single withdrawal to the original payment route.
- Make sure the payout details match the name on the account exactly.
- Watch the request status rather than filing a second one while the first is open.
- Keep the request reference number ready for any message to support.
Players who hit a stuck request often find the answer faster on www.unibet-au.org, where the status and payment steps are set out in plain words. Contact support once identity checks are complete and the request still has not moved.
Quick Reference
The table below pairs each problem with its usual cause and the first thing worth checking.
| Problem | Usual cause | First check |
|---|---|---|
| Account locked after sign-in tries | Too many failed passwords | Type the email by hand and finish any pending reset |
| Deposit missing from balance | Payment still in transit | Compare the bank reference with the transaction history |
| Phone page or game will not load | Stale cache or a blocker | Clear site cache and reload in a clean tab |
| Withdrawal pending | Open identity checks or bonus conditions | Look at the profile for unfinished steps |
| Wrong account shown | Several accounts or sessions | Sign out everywhere and sign in once |
Each row points to a single first move, which keeps the checks short. The lock row matters most because extra tries extend the block, so stop and reset instead. The deposit row depends on the bank reference, which is the one piece of evidence support cannot see without the player. The loading row is almost always local to the phone, so a second browser settles it quickly. The withdrawal row turns on identity steps and bonus conditions, which the account itself shows. Treating these as separate checks stops a payment fault from being mistaken for a login fault.
Keeping one password manager entry per account, with no autofill, prevents most lockouts and the deposit confusion that follows them.