A pending verification status means the review has not reached a final result. It does not by itself show that the documents were rejected or that the account has been approved. The useful actions during this period are limited: confirm that submission completed, preserve the request reference, monitor the official account channel, avoid duplicate uploads, and prepare a concise escalation only when the displayed timeframe has passed or the status has stopped changing.

Repeatedly submitting documents, changing profile details, opening new accounts, or creating multiple support cases can slow identification of the original request. This guide helps you distinguish normal review, incomplete submission, additional-information requests, and a genuinely stalled case.

Immediately after submission, save the information that will let you reconstruct the case:

Take a screenshot of the status page if it contains no exposed password or authentication code. Keep it privately. A clear starting point prevents uncertainty about whether the file was uploaded, submitted, or actually received for review.

An image visible in the upload control may still be waiting for the final Submit button. Reopen the verification area and look for a confirmation, review status, or request reference. If the page still invites you to add a required side or page, the set may be incomplete rather than pending.

Check the file names and categories, but do not open repeated edit sessions if the request is already under review. If a required file is definitely absent, use the designated add or replace function, or ask support whether the active request can be supplemented.

A support message may use different labels. Focus on whether an action is currently required from you.

While waiting, review your own copies without replacing them. Confirm that the document type was accepted, all required sides were included, details match the account, the document is valid, and the image is complete and readable. This prepares you to respond quickly if clarification arrives.

Use the full guide to preparing verification documents if you are unsure which aspect may be reviewed. Do not treat that review as a reason to submit another set while the first remains pending.

Do not change the registered name, date of birth, address, country, phone number, email, or payment information merely because review is taking time. A legitimate correction may be necessary, but it should be documented and made through the appropriate process. Unexplained changes during review can separate the profile from the submitted documents.

Also avoid using another person's payment method, uploading another person's document, or opening a second account. These actions do not bypass verification and can introduce additional ownership questions.

Check the verification area in the account and the registered contact channels. Review spam or filtered email folders without replying to suspicious messages. A genuine update should correspond to the active request and direct you through the official account or established support route.

Do not send a password or current one-time code in response to a message. If an unexpected sender asks for documents, verify the request inside the account before doing anything.

Use the timeframe displayed for the specific request. General time estimates from unrelated pages or other users may not apply. Weekends, document type, country, additional checks, and the need for a manual review can affect timing.

Escalate when:

Waiting is usually appropriate when the request is within its displayed period, the status is stable, and no action is requested.

Keep updates in one thread or case where possible. A timeline can be as simple as:

This lets support see the sequence without comparing separate tickets.

Read the request once from beginning to end. Identify the precise missing element: a clearer photo, reverse side, proof of address, payment ownership, live selfie, or explanation of a mismatch. Provide only that item through the designated secure route.

If the request concerns image quality, do not reuse the rejected file. Create a fresh image that fixes the stated defect. The guide to resolving a rejected verification photo provides correction steps for blur, glare, crop, missing pages, unsupported documents, and data differences.

After sending the new item, record the updated status and wait. Do not also send it through email, chat, and multiple tickets unless support explicitly instructs you to do so.

Available functions may differ depending on the reason for review and the account status. Do not assume that a feature is broken because it is temporarily unavailable. Read any banner or message attached to the restricted function.

Avoid placing transactions or bets solely to test the account. A test payment can create another pending issue. If funds are already involved, document their status without initiating duplicates.

If a deposit is also pending, keep the two timelines separate. Verification status concerns the account review; payment status concerns movement of funds. Record the payment provider reference, amount, currency, and account status independently.

Do not repeat the deposit unless both the payment provider and account show that the first attempt failed and it is safe to start again. A pending authorisation may later complete or reverse.

A withdrawal may remain pending while identity, address, payment ownership, or another account check is unresolved. Do not cancel and recreate the request repeatedly unless instructed. Record the withdrawal reference and confirm whether the account requests any action.

When the issue appears to concern transaction status rather than document review, use the related pending-withdrawal guide. Keep verification evidence in the verification case and transaction evidence in the withdrawal record, while referencing both IDs if support needs to connect them.

Keep source documents in protected storage until the case is complete. Delete unnecessary duplicate captures and remove copies from shared devices, messaging apps, and unprotected cloud folders. Do not post rejection messages or documents publicly to seek advice.

If support asks for another file, use the secure upload route. Confirm the destination from inside the account. Never include passwords, security codes, full card details, or unrelated records.

An effective message is factual and narrow:

My verification request for [category] was submitted at [time/date] under reference [reference]. The account currently shows [exact status]. The displayed review period has passed and no additional item is requested. Please confirm whether the submission is complete or identify the specific next action required.

Add the account identifier and relevant screenshot if the channel permits. Do not write a long history before stating the status and requested action.

A completed review should be reflected in the account status or an official notification. Confirm that any requested restriction is removed and the profile still contains the correct details. Do not rely solely on the disappearance of a banner; check the verification area.

If the account shows approval while a related payment or withdrawal remains pending, treat the transaction as a separate case. Verification completion does not itself prove that a transfer has settled.

Keep the original case open and record the response date. If support confirms that review continues, ask whether any action is required from you and whether the existing files remain attached. Do not respond with another document set unless the answer identifies a missing or defective item.

When no response arrives within the support channel's stated period, follow up once using the same reference. Restate the unresolved status and the last confirmed event. A useful follow-up is short: “Case [reference] remains pending; the last update on [date] said [status]. Please confirm whether an item is required from me.”

If the status changes while the case is open, update the thread immediately. This prevents a reviewer from investigating an issue that has already resolved and provides a record if a related restriction remains.

Do not treat approval as permission to leave inaccurate information. Use the profile-correction process and explain the error. Keep a record of the approved verification and the subsequent correction request.

Check the payment or withdrawal status independently. A provider can still be processing, a method can be unavailable, or a transaction can require reconciliation. Do not resubmit identity documents unless the account asks for them.

Capture the exact status and ask which category failed: document type, validity, image quality, data match, completeness, or live identity. A category-level answer is enough to choose the next action.

Check the account status, notifications, and restricted feature. The disappearance may reflect completion, replacement by another request, or a display problem. Contact support with the original reference if no outcome is visible.

Compare the categories and references. It may be an additional part of the same review rather than a duplicate. Complete only the newly requested item and reference the existing case.

Do not make avoidable profile or payment changes while identity data is being compared. If you must replace a phone number, secure an email account, or report suspicious access, state that the change is urgent and reference the verification case. Security action should not be delayed, but it should be documented so the reviewer understands why account data changed.

Similarly, do not place unnecessary transactions simply to see whether verification has finished. Use the status page and the feature's actual message. A test deposit or withdrawal creates a second process with its own references and possible review.

Once per reasonable interval, check the account status, registered email, and any requested-action banner. Confirm that your contact channels remain secure and that the original documents are available. Then stop. Constant refreshing, resubmission, and repeated chat requests do not produce a faster decision and make it harder to notice the one message that actually requires action.

Set a reminder for the end of the displayed review period. Until then, preserve evidence and avoid changes. After then, send one complete escalation under the existing case.

Use the estimate displayed for your request. Timing can vary by account, country, document, and need for manual review. Escalate after that estimate passes rather than relying on a generic number.

Only if the active request asks for it or support directs you to add it. Extra files may not accelerate review.

Availability depends on the account status and current requirements. Check the withdrawal screen and any verification message. Do not assume that submission guarantees immediate access.

A reviewer may need another side, clearer image, different document, or explanation. Open the request and identify the exact new item before uploading.

Support can clarify the process, but document assessment may remain with the designated verification workflow. Upload evidence only through the secure channel you are instructed to use.

Do not create a different version unless requested. Keep the original source document available and ask whether a fresh capture is needed.

No. It shows that the process has not reached a final result. Validity, quality, match, and completeness may still be assessed.

No. Change account data only to correct a genuine error through the appropriate process. An unexplained change can create a mismatch with the pending file.

Check whether the final submission step was completed and whether a reference exists. If the state remains unclear, contact support with the upload time, category, and screenshot.

Do not cancel automatically. Check whether the account requests cancellation or additional action. Recreating the withdrawal may reset its transaction timeline.

While review is pending, control the parts you can verify: the submission completed, account details remain accurate, contact channels are secure, and the case reference is preserved. Escalate with one precise question when the stated period passes. That approach produces a cleaner review record than repeated uploads or unrelated account changes.