Many players assume that a saved password will always work, so a rejected login on the screen feels like a hacked account. The most common cause is simply that the login details typed do not match the stored account details exactly.
Sign-in failing or the account locked after failed attempts
The player types the login details, sees an error or a blocked message, and cannot reach the account area at all.
- Login details typed with a wrong letter, spacing or capitalisation
- An old password remembered from before a change
- Too many failed attempts, which locks the account for a while
- A browser that autofills details from a different account
- A session that has expired while the page stayed open
- Type the login details by hand instead of using autofill, and keep the same spelling and capitalisation each time.
- Turn on the show-password option on the login screen and compare what appears with what was saved.
- Take a short break after a lock and try again later, because the block lifts on its own after the wait.
- Use the password reset flow with the email address tied to the account, then sign in with the new password.
- Open the site in a fresh private window to rule out stale cookies or an expired session.
- Switch from the phone browser to a desktop browser, or the other way round, and repeat the sign-in.
- Clear the saved passwords for the site in the browser settings, then enter the details manually.
- Make sure only one account exists, since a second registration under another email causes conflicts at sign-in.
- On https://bestonlinepokies-australia.com/ the account area holds the registration email, so compare it with the inbox actually used for the password reset.
- Check that the email inbox accepts messages from the site, as a full inbox blocks the reset message.
- Sign in from the same network the account was registered on, if the previous attempt came from a shared connection.
- If a lock message shows a wait time, let it run out rather than repeating the attempt.
Contact support when the reset message never arrives and the inbox is confirmed as correct.
Identity verification stuck or documents rejected
The player uploads documents, then sees the check sitting in review or a rejection note without a clear reason.
- Photographs that are blurry, cropped or show glare
- An expired document or one with a covered photo or number
- A name that differs from the account details by spelling or order
- A proof of address that is too old or shows a different address
- The file type or size not accepted by the upload form
- Retake each photo in daylit conditions with the whole document inside the frame.
- Keep all four corners visible and avoid shadows falling across the text.
- Upload the same document type again only after the earlier copy is clearly unreadable.
- Match every letter of the name to the account details before uploading.
- Use a proof of address that shows the current address and the player’s own name.
- Convert the file to a common image or document format if the form refuses it.
- Submit one document per request, so the reviewer can match each file to a field.
- After a rejection, fix the stated problem first, then resend rather than uploading more copies.
- Add the same document in a second format only when the first attempt produced no readable image.
- Let the review finish without starting a new request, since duplicates slow the queue.
- Keep a copy of every file sent, so the next step can be compared against it.
Contact support when a clear, readable document is rejected twice with the same reason.
A withdrawal pending longer than expected
The player requests a payout and the balance stays locked in a pending state with no visible progress.
- The identity check is still open, which holds the payout
- A bonus condition is attached to the balance and not yet completed
- The payout goes back to a payment route that was never used for a deposit
- Bank details saved with a wrong digit or an outdated card
- Several requests queued while an earlier one is still open
- Open the transaction history and note whether the request shows pending or in review.
- Finish any open identity check first, because the payout waits on it.
- Complete any remaining bonus condition attached to the money being withdrawn.
- Match the payout route to a route already used for a deposit on the account.
- Re-enter the bank details carefully, checking each digit against the statement.
- Cancel a duplicate request if two were made for the same balance.
- Wait for the request to move through its own stage before sending a second one.
- Keep the account balance untouched while the request is open.
- Note the request reference, so a later query points to the right payout.
- Return to the same page instead of resubmitting, as a fresh request restarts the queue.
Contact support when the request stays pending after the identity check is complete and no bonus remains attached.
Deposit or withdrawal declined because of limits
A payment is refused at the last step with a message about limits, and the balance does not change.
- The amount sits above the ceiling set for the account
- The amount falls below the smallest accepted payment
- The chosen payment route has its own cap
- The account level restricts movement until checks are done
- Repeated attempts in a short window trigger a temporary block
- Lower the amount on the payment form and send it again as a single request.
- Split a large payout into smaller requests rather than one large one.
- Raise a small amount above the minimum accepted for that route.
- Pick another payment route that accepts the amount being moved.
- Finish any open identity check, as the account level caps the money until it closes.
- Wait out a temporary block instead of repeating the attempt.
- Keep each payment inside the range the account currently allows.
- Compare the declined amount with the last payment that went through successfully.
- Note the exact message on the screen, as it names the condition involved.
- Use the phone browser rather than switching between several devices mid-payment.
Contact support when the amount is clearly within the range and the decline repeats on every route.
Keep every account detail exactly as registered from the first deposit onward; matching names, one email and consistent payment routes prevent most of these blocks before they start.