Account verification is easier when the document is valid, the account details match it, and the image lets a reviewer read every required field without guessing. Preparation matters as much as the upload itself. A correct document can still fail if a corner is cut off, glare covers the number, the image has been compressed, or the account uses a different spelling of the holder's name.

This guide helps you choose the appropriate document, compare it with the profile, create a clear image, protect sensitive files, and submit a complete set once. Document requirements depend on the account, country, payment activity, and request shown in the verification screen. Follow the request displayed in your account if it differs from a general example here.

Do not begin by uploading every document you have. Open the verification request and identify exactly what it asks you to prove. The common categories are identity, address, payment-method ownership, and a live identity check. One file may satisfy more than one category in some cases, but only the verification screen or support can confirm that for your account.

Write down these details:

If the request is unclear, ask support which category remains incomplete rather than sending additional personal information speculatively.

The examples are categories, not a guarantee that every listed item is accepted in every location. Use the on-screen list for the account. Do not alter a document to make it fit another category.

Compare the profile before taking photographs. Review the full legal name, date of birth, country, and residential address. Small differences can matter: missing middle names, reversed name order, transliteration, an old address, a typographical error, or a nickname used during registration.

Do not edit the document image to imitate the profile and do not open a second account to try another spelling. If the account contains an error, record the correct information and follow the profile-correction process. A reviewer needs a traceable explanation, not a modified image.

When names use different scripts, preserve the spelling shown on the accepted document. If the account interface requires Latin characters, use the document's machine-readable or official Latin spelling where available. Support may request clarification when multiple legitimate spellings exist.

Before capturing it, check:

A photocopy, scan of a photocopy, photo of a screen, and screenshot of a photo may lose security features and fine detail. Use the original source requested by the verifier.

Place the document on a plain, contrasting surface. Use even daylight or diffused room light. Turn off a flash that creates glare on laminated cards. Clean the camera lens and hold the device parallel to the document rather than at an angle.

The entire document should fit inside the frame with a small border around all four edges. Text must remain readable when the image is viewed at normal size. Avoid fingers covering corners, patterned backgrounds, shadows, reflections, and other documents in the frame.

For a passport, keep the identity page flat without forcing the binding. For a card, photograph the requested sides separately unless the upload interface asks for one combined file. Do not place a transparent cover over the document if it produces glare.

Use the device's normal camera mode. Portrait filters, beauty modes, document “enhancement”, artificial sharpening, and automatic redaction can change the image. Do not crop tightly or rotate repeatedly in messaging apps, because each save may reduce quality.

After capture, zoom in and inspect:

If any field is difficult for you to read, it will also be difficult for a reviewer. Retake the photograph instead of trying to repair it with editing software.

When both sides are requested, submit both even if the back appears unimportant. It may contain an address, issue authority, barcode, signature, or security data. Keep the order clear: front first, back second.

For a multi-page statement, include every page required to show the issuer, holder, address, date, and account context. Do not remove an internal page merely because it contains no transaction relevant to your request if the platform asks for the complete statement. At the same time, do not upload unrelated months or accounts that were not requested.

Name local files before upload with neutral labels such as identity-front, identity-back, and address-document. Do not put a password, full document number, or other sensitive identifier in the filename.

Identity and address checks are related but separate. An identity card may confirm who you are without proving where you currently live. Address evidence generally needs a visible name, current residential address, issuer, and recent date. The precise age limit and accepted issuers are determined by the current request.

If address evidence is required, consult the focused guide to submitting proof of address before uploading. It explains statements, digital files, household documents, address formatting, and what to do when the document is in another language.

Complete a selfie or liveness request only through the official account flow. Use a quiet, well-lit place and remove anything that hides the face unless it is required for medical or religious reasons. Follow the prompts in real time. Do not reuse an old selfie, add a filter, or ask another person to hold the account.

If the step asks you to hold a document, keep both face and document visible without covering key fields. Make sure the camera focuses before submission. A mirrored preview is normal in some apps; do not edit the image simply to reverse it unless the instructions say so.

Stop if a message asks you to send a live authentication code, password, or full payment credentials together with the selfie. Verify the request through the account's support channel.

Verification files contain information that can be misused. Capture and upload them on a device you control. Avoid public Wi-Fi where practical, borrowed phones, shared cloud folders, and messaging services used as an intermediate transfer method.

After successful submission:

Never publish a verification image in a forum or send it to a person offering paid “verification assistance”.

Repeated submission of different versions while a review is active can make it unclear which set should be assessed. If you discover a definite mistake, follow the interface's replacement option or ask support whether a new upload is needed.

Use this checklist for every file:

A document can be official yet unsuitable for the requested category. For example, a card may identify the holder but contain no current address. Return to the accepted-document list rather than repeatedly uploading the same file.

Record the exact difference. A recently changed surname, legal name change, new address, or transliteration issue may require supporting evidence or a profile correction. Do not conceal the discrepancy.

Compression, format conversion, or a weak connection may reduce quality. Compare the uploaded preview with the original. Recreate the image at a suitable resolution and upload directly rather than sending it through a messenger first.

Review the request literally. “Identity card” may require front and back; “statement” may require the page showing issuer and date as well as the page showing the address.

Do not submit the identical file. Identify the stated defect, change the capture conditions, and create a fresh image. The guide to resolving a rejected verification photo provides a symptom-by-symptom correction path.

Read the entire message and answer only what was requested. If it identifies one missing item, supply that item with the case or request reference. If the wording is general, ask which document category failed and whether the problem concerns type, validity, detail mismatch, image quality, or completeness.

A useful response includes the account identifier, verification category, submission time, current status, and a short description of what was uploaded. Do not resend every document in an ordinary chat message. Ask for the secure upload route.

Cover only information that the official instructions explicitly allow you to hide. A reviewer may need fields that seem unrelated to the user. Unauthorised redaction can make the document incomplete. For payment evidence, follow the exact masking instructions shown in the request.

Use the format requested. An original downloadable statement may contain the issuer, account holder, date, and full page context more reliably than a cropped screenshot. If screenshots are accepted, include every required element.

Acceptance depends on the current verification rules. Do not create an unofficial edited translation on top of the image. Ask whether a certified translation or an additional document is needed.

Submit it only if that document type is accepted. The absence of an expiry date is normal for some official documents, but the reviewer must still be able to confirm its validity and issue details.

No. Send the requested evidence in a complete, clear set. Unrequested files increase exposure and may slow identification of the relevant item.

Verification evidence should establish the registered account holder's identity, address, or payment ownership as requested. Another person's document usually does not prove that and may create a mismatch.

Use a current valid document and complete any live check as instructed. If the difference is substantial and review fails, explain the situation to support rather than editing either image.

Look for the submission confirmation or a status change in the verification area. Save the reference if one is displayed. An uploaded filename alone may not mean that the set was submitted for review.

Before pressing Submit, inspect the files as if you had no access to the original document. A reviewer should be able to identify the document type, read the required details, see that the image is complete, and connect it to the account without assumptions. That final two-minute review often prevents a much longer exchange about missing edges, mismatched details, or the wrong document category.