You tap the login button and the screen comes back with an error or a locked notice instead of your balance, and the most common cause is a password or username that no longer matches what the account holds. The same block often appears after several failed tries in a row.
Sign-in errors and accounts locked after failed attempts
The player types the right details and still gets an error, or the page says the account is locked and refuses to move on.
- Wrong case or a stray space copied into the username or password field.
- An old password saved in the browser or phone keyboard autofill.
- Several failed tries in a row, which triggers a temporary lock.
- Session cookies or cached pages from an earlier visit.
- Retype the username and password by hand instead of accepting autofill, and watch for capital letters.
- Clear the browser cache and cookies, then load the sign-in page again.
- Turn off any password manager or keyboard suggestion that fills the fields for you.
- Try a private window in the same phone browser to rule out stored data.
- Use the password reset link and set a new password you have not used elsewhere.
- Wait out the temporary lock before trying again, since extra attempts restart it.
- Check that the email on the account is one you can still open, because reset links go there.
- Open pointsbetlogin.org in a fresh tab if the standard page keeps looping, and sign in from there.
Contact support when the reset email never arrives and the lock will not clear after waiting.
Identity checks stuck or documents rejected
The account shows verification pending for a long spell, or a document is marked as rejected with no clear reason.
- Photos that are blurred, cropped or full of glare.
- A document whose corners are cut off or whose text is unreadable.
- Details on the document that differ from the name and address on the account.
- An expired document or one that is not accepted for proof of address.
- Files sent in a format the upload page will not take.
- Photograph each document on a flat, well-lit surface and keep all four corners inside the frame.
- Make sure the text, photo and dates are sharp before you upload.
- Match the name spelling and address exactly to what the account holds.
- Use a document that is still valid rather than one close to expiry.
- Upload one file at a time and wait for the confirmation message before the next.
- Convert the file to the format the page accepts if the upload keeps failing.
- Take a new photo instead of sending an old scan you already used.
- Keep a copy of what you sent so support can compare it later.
Contact support when the status has not changed and every document already looks clean.
Payments declined by limits
A deposit or withdrawal is refused with a message about limits, and the money never moves.
- The amount sits outside what your account tier allows for a single request.
- The method you picked carries its own cap on how much can pass in one go.
- Withdrawal rules that tie payouts to how the balance was built.
- An unfinished identity check holding the payment back.
- Daily or periodic caps already reached on the account.
- Split the request into smaller parts if the whole sum is over what your tier permits.
- Pick a different payment method if the current one has a lower cap.
- Finish any open verification step before sending a withdrawal.
- Clear older pending requests that still sit in the queue.
- Leave the balance untouched until the current request settles.
- Check the message text on the declined screen for the exact condition named.
- Retry later once a periodic cap has rolled over.
- Note down the amount and the message so support can trace the attempt.
Contact support when a request inside your own tier is still refused with no reason shown.
Deposits taken by the bank but missing from the balance
The bank shows the payment as gone, yet the casino balance stays the same.
- A pending status on the bank side that has not settled yet.
- The payment sent to an old or wrong reference.
- A deposit still held for a check before it is credited.
- Two accounts in play, with the money going to the other one.
- A browser refresh that shows a stale balance.
- Sign out and back in so the balance reloads from the server.
- Open the transaction history and look for the deposit as pending or complete.
- Compare the reference on the bank statement with the one shown in your history.
- Leave the deposit alone rather than sending it again, which can double the charge.
- Screenshot both the bank entry and the missing credit.
- Wait for the pending status to settle before you raise a case.
- Confirm you are signed in to the account that sent the money.
- Send the screenshots to support with the amount and the reference.
Contact support when the bank marks the payment complete and the balance still shows nothing.
Quick Reference
The table pairs each problem with its most likely cause and the first thing to check.
| Problem | Usual cause | First check |
|---|---|---|
| Login error | Wrong or autofilled password | Retype the details by hand |
| Account locked | Too many failed tries | Wait before another attempt |
| Verification stuck | Unclear or mismatched documents | Compare name and address with the account |
| Payment declined | Amount over the tier or method cap | Split the request or change the method |
| Deposit missing | Payment still pending | Refresh the transaction history |
A lock from failed tries clears on its own, so patience beats repeated guessing. Document rejections almost always trace back to photo quality or a name that does not match. Declined payments name the condition on screen, so read that line before changing anything. Missing deposits are usually pending on the bank side rather than lost. Refreshing the session shows the true balance in most of these cases. Keeping one clean set of documents on hand saves a second round of verification.
Set a single strong password you use nowhere else and keep your documents sharp and current, and most of these blocks never reach the screen.