Open the exchange's verification page from your signed-in account, read the requirements for your situation, and submit accurate details and accepted documents. Use clear, complete images and follow any live-capture steps. After submission, check the status and address the specific reason if review is unsuccessful.

Prepare for the request shown in your account

Before collecting documents, confirm that the request appears in the official app or authenticated website. An email can alert you to a review, but opening your account independently helps establish whether the request is genuine.

Read the accepted-document list for your country and account type. A document accepted for another person's location may not work for yours. Check expiry, required fields, and whether both sides must be visible.

Identify whether the request concerns identity, residence, or activity and funds. These categories answer different questions. A passport may establish identity without meeting a separate request for a recent residential document.

If a verification partner is used, confirm it through the provider's current help material before uploading. Inspect the URL and session context. Do not send identity photographs through an unsolicited chat merely because someone uses the exchange's logo.

Allow enough time to complete the flow without interruption. Have the document and a suitable camera ready. If the provider gives a review estimate, treat it as specific to that process rather than a guarantee copied from another platform.

Prepare evidenceSubmit securelyResolve status
Prepare evidence that fits the request, submit through the verified channel, and respond to the actual review result.

Submit the evidence step by step

  1. Open verification in the account and review the personal details already recorded. Correct genuine errors using the supported update route before submitting documents that would conflict with them.
  2. Choose the document type you actually hold and confirm it is supported. Use the original valid document when the instructions require a fresh capture.
  3. Capture the complete document with readable text and visible edges. Avoid glare, blur, fingers over important fields, and cropping that removes relevant information.
  4. Follow any selfie or live check inside the official flow. Read the instructions before starting, and keep the camera stable enough for the requested capture.
  5. Submit additional evidence only when requested and through the documented channel. Match its date range, issuing source, and identifying information to the actual request.
  6. Save the reference or submission status and return to the account for updates. Keep sensitive documents out of unnecessary copies made merely for personal progress tracking.

Diagnose rejection by its cause

An image-quality rejection calls for a better capture. Improve lighting, focus, and framing without altering the substance of the document. Uploading the same unreadable file repeatedly does not answer the problem.

An expired or unsupported document needs a currently accepted alternative. Changing the brightness of the image cannot solve a document-type restriction. Read the exact list and ask support if your valid documents are outside the listed options.

A name, birth-date, or residence mismatch requires checking the account data and the provider's update procedure. Do not make up new details to force a match. If your documents legitimately differ, establish what evidence the provider accepts to explain that difference.

A source-of-funds request needs evidence relevant to the funds being reviewed. A generic identity card does not establish a salary payment or the origin of a transfer. Describe the situation through the official review process and provide only the requested supporting records.

Some errors concern the session or device rather than the document. Follow the provider's current troubleshooting instructions for an expired session, browser issue, or phone-camera handoff. Preserve the error message so support can distinguish a technical problem from a substantive rejection.

What to do while review is pending

Check whether the provider needs more information or is still processing the submission. A pending status is not necessarily an instruction to submit another set of identical files. Read notifications within the authenticated account.

Review which functions remain available. Trading, deposits, and withdrawals can have different restrictions. Avoid moving money into an account merely because one screen remains accessible if the function you ultimately need is unresolved.

If the displayed estimate has passed or the status is unclear, contact official support with the reference and a concise chronology. State when you submitted, what was requested, and what the account currently displays.

Keep a minimal log without copying secret authentication data or identity images into an unprotected note. A date, request category, status, and case number usually provide enough context to discuss progress.

Do not pay a third party who promises to bypass the review. They cannot establish legitimate approval merely by knowing your email or case reference. Never give them account access or authentication codes to demonstrate the issue.

Confirm completion before using the account

After approval, inspect the status and any product-specific requirements. Verification may enable some services while leaving a separate payment setup or withdrawal check to complete. Read what the account actually permits.

Check the asset and funding route needed for your intended task. A completed identity process does not guarantee that every country, payment method, or token network is supported. Confirm those functions directly before a deposit.

If approval is followed by another request later, verify it through the same disciplined channel checks. Customer reviews can be ongoing and can concern different information. The fact that you previously completed a stage does not establish that every later request is fraudulent.

If you no longer want the account, inspect closure and privacy options through the provider's policy. Do not assume closing an account immediately deletes every compliance record. Ask what applies to your circumstances when that matters to your decision.

Finally, maintain account security. Identity approval and strong authentication solve different problems. Keep login and recovery channels protected so the verified account remains under your control.

Your completion record should state what was approved and what remains to be configured. It should not include document numbers, private wallet material, or emergency login codes in an ordinary shared checklist. This gives you a usable next step without creating another sensitive-data collection.

For an additional review, answer the question actually asked. If the provider requests evidence for a specific transfer, identify that transfer and the corresponding records instead of uploading a broad collection of unrelated statements. Where information about other people appears, ask what may be redacted under the documented process. Preserve the original material privately, and submit only the version permitted by the provider. This keeps the response focused while respecting the sensitivity of the information involved.

Reader questions

Can I edit a document image to make the text easier to read?

Use the provider's permitted capture process. Substantive editing or an unverifiable alteration can cause rejection; retaking a clear image is usually the appropriate image-quality response.

Should I email documents when the upload form fails?

Use only the provider's documented alternative channel. Coinbase, for example, instructs users to verify through its official flow rather than emailing ID photographs to support.

Does verification approval confirm a bank transfer has arrived?

No. Funding has its own reference and processing status. Inspect the deposit record separately.

Sources and further reading