Typing the wrong password one too many times locks the account, and the player sees a login screen that will not accept the right details anymore. The usual cause is a burst of failed attempts or a saved password that no longer matches the account.
Login Refused or Account Locked After Failed Attempts
The screen keeps rejecting the credentials or states the account is locked, and even a correct password no longer opens the lobby.
- Password typed with a different keyboard layout or a stray space.
- Too many failed attempts in a row triggered a temporary lock.
- Autofill is entering an old saved password for Rizk.
- Two-step verification code has expired before entry.
- Account details were changed at support and the old password is still in use.
- Type the password by hand into a plain text field first, so the characters are visible.
- Remove spaces at the start and end before pasting it back into the login form.
- Turn off browser autofill for the login page and enter the details manually.
- Check that the keyboard language matches the letters in the password.
- If a code is required, request a fresh one and enter it without delay.
- Use the password recovery option to set a new password with a different pattern.
- Write the new password down in a safe place before logging in again.
- Close every open tab for the Rizk kasino and start a single fresh session.
- Clear cookies for the site so an old session does not conflict with the new login.
- Wait out a temporary lock instead of sending more attempts, which extends it.
Contact support when the account stays locked after the wait or the recovery email never arrives, and ask them to unlock it directly.
Deposit Taken by the Bank but Missing on the Balance
The bank statement shows the payment left the account, yet the balance on Rizk has not changed.
- The payment is still travelling between the bank and the casino.
- The deposit went to an old or wrong payment detail saved in the browser.
- The transaction was stopped by the bank’s own fraud check.
- A bonus code was entered together with the deposit and the credit needs review.
- The deposit fell below the minimum the account accepts.
- Open the transaction history on the Rizk casino app or the browser page and look for the payment status.
- Compare the reference on the bank statement with the reference shown in the history.
- Confirm the payment was sent to the account currently logged in and not to an old one.
- Check the balance once more after signing out and back in.
- Note the exact amount, the reference and the moment of the payment for later.
- Ask the bank whether the transaction is completed or still held for review.
- Avoid repeating the same deposit while the first one is unresolved.
- Keep the screenshot of both the bank entry and the casino history side by side.
- Send the details to support in one message instead of several separate ones.
- Pause any play with the missing funds until the credit is confirmed.
When the history stays empty while the bank confirms the payment, Rizk login support can trace the reference and credit the balance; send the evidence in a single request.
Withdrawal Pending Longer Than Expected
The withdrawal shows as pending while the balance stays unchanged and the request does not move forward.
- Account checks are still open and need documents from the player.
- A bonus is attached to the funds and play conditions are not finished.
- Deposit funds have not cleared yet, so the payout waits behind them.
- The chosen payout route does not match the deposit route.
- A pending request was cancelled by a second click and hidden in the history.
- Open the withdrawal history and confirm the request is still pending rather than cancelled.
- Upload any requested identity documents in the account area as a clear photo.
- Check whether a bonus is still active and finish the remaining play conditions.
- Leave the request in place instead of cancelling and resubmitting it.
- Use a payout route that matches the method used for the deposit where possible.
- Confirm the payout details are complete and belong to the player.
- Look for any message from the payments team in the account inbox.
- Wait for the deposit to clear before expecting the withdrawal to move.
- Gather the request number, the amount and the date in one note for support.
Contact support when the request stays pending with no document request and no message explaining why.
Site or Games Not Loading Properly on a Phone
The lobby opens slowly, games freeze or the page loads without images, all inside the phone browser.
- Weak mobile data or a crowded Wi-Fi network.
- A browser version that is out of date or too old for the page.
- Cache and cookies holding a broken copy of the site.
- A game provider blocked by an extension or a private network filter.
- Too many tabs and background pages using the phone’s memory.
- Close the tab and open the site again in the phone browser.
- Switch between Wi-Fi and mobile data to see which connection works.
- Clear the browser cache and cookies, then sign in again.
- Update the browser to the newest version available for the phone.
- Disable extensions or content blockers for the site.
- Close other tabs and background pages to free memory.
- Try a single game first instead of opening several at once.
- Restart the phone and open the lobby with a clean session.
- Try a different browser on the same phone to separate a site issue from a device issue.
Contact support when one game fails in every browser while others load fine, and name the game in the message.
Quick Reference
The table below pairs each problem with the cause that most often explains it and the first thing to check.
| Problem | Usual cause | First check |
|---|---|---|
| Login refused | Saved password out of date | Type the password by hand |
| Account locked | Too many failed attempts | Wait out the temporary lock |
| Deposit missing | Payment still travelling | Transaction history status |
| Withdrawal pending | Open account checks | Document request in the account |
| Phone page broken | Old cache in the browser | Clear cache and reload |
A lock from failed attempts clears itself once the attempts stop, so patience is part of the fix. Deposit checks should start in the transaction history rather than at the bank. Pending withdrawals often move once the requested documents reach the payments team. Phone problems usually sit in the browser, not in the account. A single clear message to support with the reference numbers saves a long exchange. Playing in one clean browser session prevents most of these conflicts.
Keep one written record of the login details, the payment references and the answers given by support, and update it after every change, so each new problem starts from known facts.