A payment screen shows your deposit or withdrawal marked as declined, and the cause is usually a rule attached to your account rather than a fault in the payment itself. The same applies to a withdrawal that sits pending or a login form that will not accept your details.

Deposits and withdrawals declined by account limits

The payment screen returns a declined message just after you confirm the amount.

• The amount falls outside the range allowed for the payment route you chose.
• A limit attached to your account has already been reached for the period.
• The payment method belongs to someone other than the account holder.
• Your account details and the payment details do not match.
• A bonus condition restricts how much can be withdrawn while it is active.

1. Note the exact amount you tried to send and the route you used.
2. Try a smaller amount on the same route to test the lower boundary.
3. Switch to another payment route that accepts the amount you want.
4. Make sure the payment account carries your own name.
5. Compare the name and address on the payment account with your Mystake profile.
6. Correct any difference in spelling or address before trying again.
7. Check whether an active bonus blocks withdrawals above a set size.
8. Complete any bonus playthrough first if you want the full balance out.
9. Confirm that your account has passed identity checks before a large withdrawal.
10. Split a large request into smaller ones if a single-request cap applies.
11. Wait for any earlier pending request to finish before sending another.
12. Keep a screenshot of the declined message with the amount and route shown.
13. Retry once after correcting the cause, then stop repeating the attempt.
14. Contact support with the screenshot if the decline continues after your fix.

Contact support when the decline repeats with a correct amount and your own payment method, or when no message explains the limit.

A withdrawal that stays pending past the stated window

The withdrawal list shows your request as pending while the balance has already left your playable funds.

• Identity checks are still open on the account.
• An earlier withdrawal is already in the queue ahead of yours.
• A bonus condition has not yet been met.
• The payment details on file are incomplete or need reconfirming.
• The request was made during a period when the payment route is unavailable.

1. Open the withdrawal history and note the status and timestamp of the request.
2. Check your messages for a request for documents or extra details.
3. Send any requested identity document in a clear, readable image.
4. Finish any open bonus playthrough before expecting the funds to move.
5. Confirm that your payment details are complete and current.
6. Avoid sending a second request while the first is still pending.
7. Allow the stated window for the payment route to pass before you worry.
8. Use your phone browser to log in to https://mystakeuk.org/ and read the status there.
9. Reply to any message from the payment team with the missing item.
10. Keep the reference number of the request ready for any contact.
11. Stop cancelling and resending the request, as this moves it to the back.
12. Note what each status change means so you can describe it later.
13. Contact support when the window has passed and the status has not moved.

Contact support once the stated window ends with the status unchanged, or at once if a pending request is paired with an unresolved document request.

Games and pages that fail to load on a phone

A game screen shows a blank area, a spinning loader or an error page while the rest of the site seems reachable.

• The phone browser is out of date or has stored bad data.
• The connection is weak or switches between networks mid-load.
• The game is heavy and the phone is low on memory.
• Background tabs are using the connection at the same time.
• An ad blocker or privacy extension is blocking game scripts.

1. Reload the page once and watch whether the loader completes.
2. Close other tabs and background apps to free memory and bandwidth.
3. Clear the browser cache and stored site data.
4. Update the phone browser to its current version.
5. Move to a stable connection before you open the game again.
6. Disable any ad blocker or privacy extension for the site.
7. Allow scripts and cookies for the site in your browser settings.
8. Try the same game again in a private browsing window.
9. Test a lighter game to see whether the fault is specific to one title.
10. Restart the phone if pages keep loading halfway.
11. Keep the browser zoom at its default level, as some games misdraw at odd sizes.
12. Update the phone system if pages break after an update.
13. Retry later if only one game fails, since that title may be under maintenance.
14. Contact support with the game name and a screenshot if the fault follows you across browsers.

Contact support when one game fails on every browser and connection you try, or when the whole site fails on mobile data and Wi-Fi alike.

Login refusal and a locked account after failed attempts

The login form returns an error, or the account page shows a lock after several wrong tries.

• The password or username carries an extra space or wrong capital letter.
• Several failed attempts triggered a short lock.
• Two-factor codes are being rejected because the phone clock is off.
• You are signed in on a device that still holds the old session.
• The account is paused while a security check is reviewed.

1. Retype the username and password by hand instead of pasting them.
2. Watch for spaces at the start or end of either field.
3. Match the capital letters exactly as you registered them.
4. Try the password reset route before you make more attempts.
5. Follow the reset message and set a new password you have not used before.
6. Wait out the short lock if the message says attempts are limited.
7. Correct the phone time so two-factor codes match.
8. Sign out of all devices, then sign in on one device only.
9. Clear cookies for the site if the login page keeps returning you to itself.
10. Switch to your phone browser if the desktop one misbehaves.
11. Type the one-time code as soon as it arrives, before it expires.
12. Use a password manager to avoid typing errors in future logins.
13. Note the exact error text so support can identify the lock type.
14. Contact support when the lock persists after the wait and a successful reset.

Contact support when the reset succeeds but the lock remains, or when no error text explains why the login fails.

Use one password manager entry and one set of payment details that match your profile, and most of these blocks never appear.