After several failed attempts, the screen shows that your account is locked, and the usual reason is a simple mistyped password rather than a ban. The lock is a safety measure that triggers when the login form receives repeated wrong credentials.
Account lockouts and failed sign-in attempts
The player sees a message that the account is locked or that the password is incorrect, and the form refuses further tries. The most common causes are below.
- A password typed with the wrong keyboard layout or caps lock on.
- Saved autofill details that no longer match the current password.
- Several rapid attempts that triggered the lockout rule.
- An email address entered with a typo or an old address.
- A session that expired while the page stayed open in another tab.
Work through these steps in order.
- Close every open tab of the site and open a fresh browser window.
- Type the email address by hand instead of using autofill.
- Check the keyboard language and turn off caps lock before typing the password.
- Use the password recovery link on the sign-in form if the password is forgotten.
- Follow the reset link sent to your email inbox, and check the spam folder if it is missing.
- Set a new password that you have not used on this account before.
- Sign in once with the new password and no other tabs open.
- If the lock message remains, wait for the lockout period to pass before trying again.
- Avoid repeated attempts during the wait, because each one can extend the lock.
- Clear the browser cache and cookies if the form still rejects correct details.
- Try a different browser or a private window to rule out stored data.
- On a phone browser, switch off any password manager that fills the form automatically.
- Confirm that the email address on the account is one you can still open.
- Change the password from a device you have used before for the Mystake login.
- Write the new password down in a safe place instead of relying on memory.
- If the account stays locked after the wait and a correct password, gather the email address and the exact message shown.
- Contact support with those details when self-service steps no longer change the result.
Contact support when the lock persists after the waiting period and a password reset, or when you suspect someone else tried to sign in.
Pending withdrawals that take longer than expected
Players see a cashout marked as pending while the balance stays unchanged, and the usual cause is an unfinished check on the account or a payment detail that does not match. mystake2.net/ handles these requests in a queue, so a pending status is normal for a while.
- Identity verification has not been completed on the account.
- The payout method details differ from the name on the account.
- Bonus funds are still tied to playthrough conditions that are not met.
- A previous cashout is still being handled, and only one can run at a time.
- The request was sent outside the hours when payouts are reviewed.
Use these steps to move the request forward.
- Open the cashier and read the status of the pending request.
- Check that the account has passed identity verification before requesting again.
- Compare the payout details with the name and address on the account.
- Finish any bonus playthrough that is still active on the balance.
- Cancel a duplicate request if the cashier shows more than one pending cashout.
- Wait for the review window that applies to your request before sending a message.
- Take a screenshot of the pending status and the amount shown.
- Contact support with the request reference and the screenshot attached.
- Reply to any message from the checks team on the same day it arrives.
- Send documents only through the secure upload in the account, not by email.
- Keep the payout method active until the money arrives.
- Avoid starting a new cashout while the current one is still pending.
- If the status changes back to balance, read the reason shown in the cashier.
- Fix the reason before sending the request again.
- Note the date and time of each new request for your own records.
- Contact support when the request stays pending well beyond the stated review window.
Reach out to support when the pending request shows no change after the review window and all verification steps are complete.
Deposits and withdrawals declined by limits
The cashier declines the transaction and shows a message about a limit, which often comes from the account level rather than the payment method. The common causes are listed next.
- The amount is above the ceiling set for the account.
- The amount is below the minimum the cashier accepts.
- A daily or weekly total has already been used up.
- A self-imposed limit set by the player is still active.
- The payout method has its own cap that differs from the site rule.
These checks help you get the transaction through.
- Read the exact message in the cashier and note the limit it names.
- Compare the amount you entered with the minimum and maximum shown on the form.
- Lower the amount to fit under the ceiling and send it again.
- If a daily total is used up, wait for the period to reset before another try.
- Review any deposit limit you set yourself in the account settings.
- Change a self-imposed limit only through the process the account offers.
- Split a large cashout into smaller requests only if the cashier allows it.
- Use a payout method whose own cap fits the amount you want.
- Check that the currency of the request matches the currency of the account.
- Remove a saved payment detail that no longer works and add it again.
- Try the transaction in a fresh browser window with no other tabs open.
- On a phone browser, disable any script blocker that could interrupt the form.
- Keep a note of the message shown for each declined attempt.
- Wait for the reset period before trying the same amount again.
- Do not open several requests in a row to get around a limit.
- Contact support with the messages and the amounts when the decline repeats.
- Ask support to explain which limit applies to your account level.
Contact support when the decline repeats with amounts that fit the limits shown and no self-imposed limit is active.
Stuck identity verification and rejected documents
The account shows verification as pending or the uploaded document is marked as rejected, and the usual reason is a photo that is unclear or a document that does not match the account details. The likely causes follow.
- A photo with glare, blur or a corner of the document cut off.
- A document that has expired or is not the type requested.
- The name or address on the document differs from the account.
- A selfie taken with a filter or in poor light.
- An upload that failed and left the check waiting for a file.
Follow these steps to clear the check.
- Open the verification section of the account and read which document is requested.
- Take the photo on a flat surface with even light and no flash glare.
- Include all four corners of the document in the frame.
- Check that the document is still valid and shows your current name.
- Upload the file in the format the form accepts.
- For a selfie, remove hats, glasses and filters and face a window.
- Make sure the account name matches the document exactly, including middle names.
- If the address differs, add a proof of address that shows the current one.
- Upload one document at a time and wait for the status to change.
- Do not send the same file again while the first upload is still pending.
- Keep the original files on your device in case a new upload is needed.
- Check the inbox tied to the account for a message about a missing file.
- Reply to that message with the requested document through the secure upload.
- If a document is rejected, read the reason and fix only that issue before resubmitting.
- Submit a different document type only if the form offers that choice.
- Note the date of each submission and the status shown after it.
- Contact support when the status stays pending after a full set of clear documents.
Contact support when a clear and valid document is rejected more than once without a reason you can act on.
Keep one dedicated email inbox, one password manager entry and one set of clear document photos ready, and most of these blocks never reach the support queue.