KYC means Know Your Customer. On a crypto exchange, it is the process of collecting and verifying information about an account holder. Requirements depend on the provider, product, and applicable rules. Confirm the official submission channel and purpose before sending identity documents.

What the exchange is trying to establish

Identity checks can help a provider determine who controls an account, whether the person is eligible for a service, and whether further information is required. Exchanges describe legal, compliance, and fraud-prevention purposes for these processes.

The initial request commonly concerns personal details and identity evidence. Further reviews may ask about residence, activity, or the origin of funds. A request for a specific document should explain what information the provider needs and how it should be supplied.

KYC is part of an account relationship that can continue after signup. A provider may request updated information or additional verification later. The exact reason and required action should be checked through the authenticated account or official support.

Requirements are not identical across countries or services. An accepted-document list does not establish that the platform offers every product in the document holder's country. Check eligibility separately from the ability to upload a passport or identity card.

Request verifiedInformation submittedAccount status
Verify the identity request, submit through the official process, and check the resulting account permissions.

What you may be asked to provide

A provider may request your legal name, date of birth, residential details, and a supported government-issued document. It may also use a selfie or live capture to compare the applicant with the document. Follow the current instructions for your location.

Proof of residence is a separate category when requested. Read acceptable document types, date requirements, and matching details. A document suitable for proving identity may not meet the provider's residence requirements.

Source-of-funds information concerns where particular funds originated. Source of wealth can ask a broader question about how assets were accumulated. If a request is unclear, ask the provider which category applies and what evidence answers it.

Supply accurate information and current documents that belong to you. If your situation includes different issuing and residence countries, use the provider's support process to establish what is supported. Changing details merely to fit a form can create further account problems.

Avoid sending extra documents that were not requested. Review the provider's privacy information and any named verification service. You should be able to identify who is collecting the data and where the submission is being made.

Verify the request before uploading

  1. Open the exchange independently using its official app or a known website address. Sign in and check whether the verification request appears in the account.
  2. Read the stated purpose, deadline, supported documents, and affected functions. If an email describes a request that is absent from the account, confirm it through official support.
  3. Inspect the upload domain and any named verification partner against the provider's current help documentation. Logos, search advertisements, and familiar-looking email text are insufficient proof.
  4. Prepare only the required material and submit it through the documented flow. Follow image-quality instructions without altering the substantive document information.
  5. Keep the case reference and check the status in the account. If the request is rejected, read the specific reason before starting another attempt.

How to handle a request that does not fit your circumstances

An expired document, inconsistent personal detail, or unsupported document type can prevent completion. Capture the exact error and compare it with the instructions. A sharper image cannot resolve an eligibility issue, while an eligibility explanation cannot fix an unreadable photograph.

If your legal name, residence, or document changed, use the documented update process. Find out whether the provider expects an account-detail change before another identity submission. Maintain the original records in case support needs to understand the sequence.

Repeated attempts can trigger temporary restrictions on some services. Check any displayed waiting period rather than continuing to upload identical material. Support can explain the next permitted step through the official channel.

If funds are already in the account, inspect which functions are restricted. Trading permission, deposit availability, and withdrawal access can have different conditions. A verification status alone does not answer whether a particular balance is currently withdrawable.

Preserve transaction and account references. If you contact support, describe the request and the blocked action precisely. Do not send authentication codes, passwords, or a wallet recovery phrase as evidence of identity.

Privacy and account security are separate decisions

Identity documents are sensitive data. Before choosing a provider, examine its privacy notice, the processing purpose, and any available information about retention and service partners. If an important point is unresolved, seek clarification before submission.

A legitimate request can still deserve scrutiny about how much information is necessary. Ask what must remain visible and whether any redaction is allowed. Follow the stated rules rather than editing a document in a way that makes verification impossible.

Completing KYC does not replace strong authentication. Protect your exchange login, email account, and recovery channels. An account can have verified identity information and still be exposed through a stolen password or compromised device.

Verification also does not establish that a token is suitable, a trade is profitable, or a provider is financially sound. Those questions require separate evidence. An identity badge describes an account process with a specific scope.

If someone contacts you privately offering guaranteed approval for a payment, reopen the exchange's support flow yourself. A third party should not need control of your account to help you read a public document list.

When the process finishes, review the actual permissions and limits shown in your account. Keep a record of what was completed and which questions remain unresolved. This gives you a practical basis for deciding whether the provider supports the task you intended to perform.

Keep a minimal verification log containing the date, the category of information requested, the official channel used, and the resulting status. Avoid copying document numbers or identity images into an unnecessary second location. If a later request arrives, the log helps you explain what was previously submitted without exposing the documents again. For a rejected submission, record the exact reason and the proposed correction. Separate a technical upload failure from a request for new evidence or an unsupported location. Those issues require different responses, and repeatedly changing unrelated details can make the review harder to understand.

If you no longer intend to use the service, inspect its account-closure and data-request options. Closing an account and deleting all retained records can have different conditions under the provider’s published policy.

Reader questions

Does a self-custody wallet always require the same KYC as an exchange?

Wallet software and custodial services can have different roles and requirements. A purchase integration inside a wallet may run its own identity process.

Can KYC approval be transferred to another exchange?

Do not assume so. Each provider applies its own process unless it explicitly supports a recognized verification arrangement.

Is an email asking for ID automatically a scam?

Not necessarily. Verify the request by opening your account independently and following the provider's documented channel before sharing anything.

Sources and further reading