You mistyped the password once too often, and now the sign-in screen answers with a lock instead of your balance. Failed attempts hitting a security threshold is the usual reason, not a lost account.
Documents Stuck in the Identity Check
The upload screen keeps showing your files as pending, or a rejection message returns without saying which photo failed.
- A photo is blurred, cropped or shows glare across the text.
- The name on the document does not match the name on the account.
- Only one side of a two-sided document was sent.
- The document has passed its expiry date.
- The file type or size falls outside what the upload form accepts.
- Place the document on a flat, dark surface in daylight and photograph it straight on, with all four corners visible.
- Send every page or side the form asks for, even when one side looks blank.
- Use the full legal name exactly as printed, including middle names and hyphens.
- Re-send a rejected file as a fresh photo rather than the same image compressed again.
- Close other tabs on the upload page and wait for the confirmation message before leaving.
- Keep the original document to hand while the check is open, in case a second copy is requested.
Contact support when the same file is rejected twice with no reason given, or when the status has not moved at all.
Locked Out After Failed Sign-In Attempts
The login page accepts your username but refuses the password, then blocks further attempts and may ask for extra confirmation.
- Caps lock or a phone keyboard that capitalises the first letter silently changes the password.
- An old password saved in the browser autofills over the correct one.
- Too many wrong attempts in a row triggered the lock.
- The account email was changed and the confirmation link was never opened.
- A password reset was requested but the new one was never saved.
- Type the password by hand into a plain text field first, so you can see exactly what the keys produce.
- Clear the saved password for the site in your browser, then reload the sign-in page.
- Use the forgotten-password link and open the message on the same device you will sign in from.
- Set a new password you have not used on the account before, then save it in your password manager.
- Sign in once on a stable connection and let the page finish loading before tapping anything else.
- If a confirmation code is requested, enter it promptly and do not request a second one meanwhile.
Contact support when the reset message never arrives or the account stays locked after a successful reset.
Withdrawals Sitting as Pending
The cashier shows the request as pending while your balance stays reduced, and nothing moves for longer than you expected.
- An identity or address check is still open on the account.
- Bonus funds were still active when the request was made.
- The payout details do not match the name on the account.
- A previous withdrawal request is still being handled.
- The request was made at a busy time and sits in a queue.
- Open the transaction history and note the exact status wording, not just the amount.
- Finish any open document request before sending a second withdrawal.
- Confirm the payout details are saved as the default method, not a saved but unused one.
- Withdraw only from cleared cash, after any bonus play has finished.
- Cancel a duplicate pending request only if the cashier allows it, rather than stacking several.
- Wait for the status to change before contacting anyone, and keep the reference number.
Contact support when the status has not changed while every condition above is already met, or when the balance is held twice.
Games and Pages Misbehaving on a Phone
The lobby loads but a game stays on a blank screen, spins forever or drops back to the menu mid-round.
- The mobile browser is outdated or has scripts blocked.
- Cached data from an earlier visit conflicts with the current page.
- The connection drops when the phone switches between Wi-Fi and mobile data.
- Too many tabs or background apps are competing for memory.
- A game needs more resources than the phone browser can give it.
- Close every other tab, then reload the page in a current version of your phone browser.
- Clear the browser cache and cookies for the site, then sign in again.
- Turn off battery-saving mode, which can pause scripts in the background.
- Switch off the phone’s data connection and stay on one stable network for the whole session.
- Open a different game from the same provider to see whether the fault travels with one title.
- Reduce the browser zoom to the default and rotate the phone back to portrait.
- Log in to https://jackpot-village.me.uk/ in a private browsing window to rule out stored data entirely.
Contact support when one game fails on every network while others open fine, and mention the game name.
Quick Reference
Each row pairs the screen symptom with the cause most often behind it and the first thing worth checking.
| Problem | Usual cause | First check |
|---|---|---|
| Documents pending or rejected | Unclear photo or mismatched name | Re-shoot in daylight with all edges visible |
| Account locked at login | Repeated wrong passwords | Retype the password by hand |
| Withdrawal pending | Open identity check or active bonus | Read the transaction status |
| Game freezes on phone | Stale cache or weak connection | Clear cache and reload in the browser |
| Balance held twice | Duplicate withdrawal requests | Count the pending entries in the history |
Document problems almost always come down to image quality, so a sharp, straight photo resolves most rejections before support is needed.
Login locks are self-inflicted more often than not, because autofill quietly supplies an old password each time.
Pending withdrawals are not a fault in themselves; they reflect open checks or unsettled bonus play.
Phone faults usually follow stored browser data, which is why a private window is a quick test.
A duplicate request is the one case where the balance can look wrong even though nothing has failed.
When you contact support, give the transaction reference or the game name so the matter can be traced quickly.
Sign out properly at the end of each session on a shared phone, and let the page confirm the sign-out before closing the browser.