You are staring at a KYC screen that says your document was rejected, or a login box that keeps returning you to the same page. Most of these cases trace back to a small mismatch between what you typed and what the account expects.

Identity checks that stall or get documents rejected

The verification page shows your upload marked as rejected or stays stuck on pending for a long stretch. The usual culprit is a photo that is blurred, cropped or shows glare across the printed data. Common causes:

• The photo is cut off at the edges, so the full document outline is missing.
• Light reflection or shadow hides part of the text or your face.
• The name on the document differs from the name entered during registration.
• An expired document was uploaded instead of a current one.
• A single file was sent when both sides of the document are needed.

What to do:

1. Place the document on a flat, dark surface in daylight and avoid the camera flash.
2. Capture the whole document, including all four corners, and make sure the text is sharp.
3. Photograph both the front and the back if the document has information on each side.
4. Keep your fingers out of the frame so nothing covers the printed details.
5. Compare the name, spelling and date of birth with what your account holds.
6. If the account name is wrong, do not register a second account; ask support to correct it.
7. Upload the corrected images in the same section where the rejected file sits.
8. Submit one clear file per slot instead of a collage of several images.
9. Check the file size and format the upload field accepts before you send it.
10. Wait for the review to finish before uploading a second version of the same document.
11. Keep a copy of every file you send so you can resend it if needed.
12. Make sure the selfie, if requested, shows your face clearly without a hat or filter.
13. Use the same document type throughout the process rather than switching mid-way.
14. Remove any case covers or sleeves that obscure the document edges.
15. Reopen the page in your phone browser if the upload button does not respond.
16. Contact support once two clear uploads of the same document have been refused.

Write to support when your documents are sharp and complete but the status still does not move.

Locked accounts and failed sign-in attempts

The sign-in form refuses your password and after several tries it tells you the account is locked. Wrong credentials and repeated quick retries are the two most frequent reasons. Common causes:

• The password was typed with the wrong keyboard layout or with Caps Lock on.
• The email address has a typo or uses a different spelling than the one registered.
• Too many failed attempts in a short window triggered a temporary lock.
• Saved credentials in the browser are outdated after a password change.
• You are on a shared or public device where the session was ended by someone else.

What to do:

1. Retype the password by hand instead of pasting it, watching for stray spaces.
2. Switch the keyboard layout and turn off Caps Lock, then try once more.
3. Confirm the email address character by character against the one you registered.
4. Clear the saved password for Jokabet in your browser and enter it fresh.
5. Stop retrying after a few failures, because each attempt can extend the lock.
6. Use the password reset option and open the reset message in the same browser.
7. Set a new password you have not used on other sites.
8. Avoid special characters your keyboard may render differently on another device.
9. Write the new password down somewhere private before you save it.
10. Close other browser tabs on the same site so only one session is open.
11. Turn off any VPN or proxy that changes your apparent location between attempts.
12. Try the phone browser with mobile data if your home connection keeps failing.
13. Allow the lock period to pass quietly rather than hammering the form.
14. Sign in once and stay on the page until the account area loads fully.
15. Contact support if a correct password and a completed reset both fail.

Ask support for help when the reset link does not arrive or the lock outlasts a normal wait.

A withdrawal that stays pending

The withdrawal shows as pending in your history while the balance has already been reduced. Unfinished verification or a bonus still in play is the most common reason it sits there. Common causes:

• Identity verification was never completed or is still under review.
• A deposit made shortly before the request has not settled yet.
• Bonus funds are still tied to play requirements that are not met.
• The payout details do not match the name on the account.
• Several requests were queued at once, which slows the queue.

What to do:

1. Open your withdrawal history and read the status note next to the pending request.
2. Finish any verification step that is still marked as open.
3. Confirm the payout destination is registered in your own name.
4. Check whether a bonus was active when you placed the request.
5. Complete the remaining play on that bonus before requesting again.
6. Avoid depositing more while a withdrawal is waiting, as it can reset the review.
7. Cancel duplicate requests so only one stays in the queue.
8. Leave the balance untouched until the pending request is resolved.
9. Make sure the amount is above the smallest payout the account allows for that route.
10. Sign out and back in to refresh the status rather than refreshing the page many times.
11. Note the time you submitted the request so you can describe it to support.
12. Take a screenshot of the pending entry and of the balance beside it.
13. Wait for the stated review window to pass before assuming something is wrong.
14. Reply to support with the screenshot instead of opening a second ticket.
15. Do not start a new withdrawal from a different device while one is pending.
16. Contact support when the status has not changed after the review window ends.

Reach out to support once the pending request outlasts the normal review period with no change.

Payments declined by account limits

The payment screen rejects the amount and points to a limit rather than a card or bank error. Most declines come from a cap linked to your account level or payment route. Common causes:

• The amount sits above the ceiling set for that payment route.
• The account level carries a lower deposit or payout cap than you expect.
• Several payments in a short period hit a daily or weekly ceiling.
• Part of the balance still comes from a bonus with its own cap.
• A currency mismatch makes the converted amount exceed the limit.

What to do:

1. Read the exact message on the decline screen and note which limit it names.
2. Lower the amount and resend it to see whether the limit is the cause.
3. Split a large request into smaller ones spaced over time if the route allows it.
4. Pause new deposits if you have made several within a short window.
5. Check whether an active bonus covers the funds you are trying to move.
6. Finish the bonus play so the balance becomes fully yours to withdraw.
7. Use a payment route that matches your account currency where possible.
8. Keep the payout amount inside the range the account permits.
9. Avoid switching routes back and forth to dodge a limit, as this delays review.
10. Look at your account level and what it allows before sending a large amount.
11. Record the declined amount and the message for your own reference.
12. Try again later in the day if a daily cap is the reason.
13. Make sure the receiving details belong to you and are entered without errors.
14. Stay on one route for the next few payments so the pattern looks consistent.
15. Ask support about your account level if you need a higher ceiling.
16. Contact support when a decline names a limit you cannot trace to your own activity.

Get in touch with support when the message points to a cap on your account that you did not set.

Keep your registered name, your document and your payment details identical in spelling, and almost every check above will clear on the first try.