When a crypto exchange requests source-of-funds documents, it asks you to show where particular money or crypto came from and how it reached your account. It is not automatically an accusation. Treat it as a controlled evidence task: verify the request through the exchange's official channel, identify the transactions in scope, submit only relevant records, and preserve an exact copy of what you sent.

Key Takeaways

Verify the case inside the official app or website before opening links or uploading documents.

Source of funds explains a specific transfer; source of wealth explains how a person's overall wealth was accumulated.

Build a chronological evidence chain connecting the origin, intermediate accounts and exchange deposit.

Redact unrelated sensitive data only when the exchange permits it, without hiding names, dates, amounts or identifiers needed to verify the trail.

If the request is unclear or rejected, ask for the missing requirement and formal review path in writing.

This guide explains safe record preparation, not how to bypass customer due diligence. Exact evidence, retention and appeal rules depend on the exchange, account type and applicable law.

Why does a crypto exchange ask for source-of-funds documents?

Exchanges may review activity to meet customer due-diligence, anti-money-laundering, sanctions and fraud-control obligations. A review can follow a large or unusual deposit, a rapid change in activity, transfers involving higher-risk services, a mismatch with the account profile, or routine periodic monitoring. FATF's virtual-asset red-flag indicators describe patterns that can merit closer examination, but a red flag is a prompt for analysis rather than proof of crime.［1］

The EBA says crypto-asset service providers should use risk-sensitive measures and consider customers, products, delivery channels and geography.［2］ EU anti-money-laundering rules also illustrate why a regulated firm may need to understand the purpose of a relationship and conduct ongoing monitoring.［3］ Other jurisdictions use different statutes and terminology.

Support should identify the case, transactions, submission channel and deadline; the request alone does not determine the outcome.

How do you verify that the request is genuine?

Do not trust an email, direct message, phone number or upload link merely because it uses the exchange's logo or knows your name. Compliance-themed phishing can exploit the urgency of an account review.

Open the exchange app from your device or type its known website address yourself.
Check the in-account notification, support center or case history for the same reference.
Contact support through that authenticated session if the request is missing or inconsistent.
Confirm the exact upload domain, accepted formats, deadline and whether encrypted archives are allowed.
Never disclose a password, one-time code, seed phrase or private key. Those are not proof of funds.

If a caller asks you to transfer crypto to a “verification wallet,” stop. Moving assets to a stranger is not document verification. The broader online security guide explains how to re-enter a service independently instead of following an alert's link.

What is the difference between source of funds and source of wealth?

Source of funds concerns the origin of assets used in a specific transaction or group of transactions. Examples include salary saved in a bank account, proceeds from selling an asset, revenue from a business, a documented gift, an inheritance, mining income, or crypto purchased earlier on another platform.

Source of wealth is broader. It describes how your total wealth was built over time, such as employment, ownership of a business, long-term investing or inherited assets. An exchange may ask for one or both, but the evidence is not interchangeable.

A bank statement can prove movement without explaining why the sender held the money; an employment contract can explain income without connecting it to a purchase. A strong response joins origin and movement without disclosing unrelated history.

Which documents might support a source-of-funds explanation?

The right package depends on the stated origin. Common evidence categories include:

Claimed origin	Possible supporting evidence	Connection still needed
Employment income	Payslips, employment record, tax statement, bank credits	Transfer from the receiving bank account to the purchase or exchange
Sale of property or another asset	Sale agreement, completion statement, account credit	Subsequent bank or crypto movement
Business income	Invoice, contract, company record, business bank statement	Ownership and transfer into the relevant account
Gift or inheritance	Gift letter, estate record, probate or distribution statement	Donor or estate payment and your receipt
Purchase on another exchange	Trade export, account statement, withdrawal record	Matching destination address, asset, amount and time
Mining, staking or protocol activity	Wallet addresses, reward history, pool or protocol records	Control or ownership of the wallet and later deposit path
Peer-to-peer transaction	Platform order, counterparty record, payment receipt	Matching bank payment and crypto transfer

This is not a universal acceptance list. Ask the exchange which records it accepts for your case. Self-created spreadsheets can explain a calculation but rarely replace original statements, transaction exports or legal records.

How do you build a clear source-of-funds evidence chain?

Start with the exchange's questioned deposit and work backwards. Record the asset, amount, transaction identifier, network, sending address or account, receiving address, timestamp and any fee. Then identify every earlier step until you reach the stated economic origin.

Create a short index such as:

Salary credited to bank account on 4 May.
Bank transfer sent to Exchange B on 10 May.
Asset purchased on Exchange B on 10 May, with order identifier.
Withdrawal from Exchange B on 12 May, with transaction hash and fee.
Deposit credited by Exchange A on 12 May.

For each step, attach the original export or statement and highlight the matching line without altering its contents. Use consistent time zones and explain asset symbols that changed. If several trades or wallet hops are involved, the crypto trade history reconciliation guide shows how to pair transfers without counting them as new income.

Blockchain explorers can corroborate an on-chain movement, but they normally do not prove who controlled an address or why the transfer occurred. Account statements and ownership evidence supply that missing context. The distinction also matters when comparing a self-custody wallet with an exchange account.

How can you submit documents without exposing too much?

Use the exchange's authenticated upload facility whenever possible. Keep originals unchanged in your archive and submit copies in the requested format. Before uploading, inspect every page, including hidden spreadsheet columns, PDF attachments, comments and image metadata.

Minimize data carefully. Remove unrelated transactions, account numbers or third-party details only if the exchange's instructions permit redaction. Never obscure the fields needed to connect the evidence: your name, issuer, statement period, relevant dates, amounts, transaction identifiers and account ownership may all be material. Mark a redaction visibly rather than cropping a page so aggressively that its authenticity becomes impossible to assess.

Do not send a seed phrase, private key, password, authentication code, full card security code or remote-access session. If support requests unusually sensitive material, ask why it is needed and whether a safer alternative is accepted. Follow the sensitive data protection guide when storing the response package.

Use a dedicated case folder, document index and copy of the request. Avoid public file-sharing links and check cloud permissions and expiration.

What should your written explanation include?

Write a factual cover note, not a long defense. State the case reference, transactions covered, source category, chronological route and attachment mapping. Explain discrepancies such as fees, exchange-rate differences, internal transfers, name variations or a wallet hop.

Separate known facts from estimates. If a record is unavailable, say which record is missing, why, what you did to retrieve it and which alternative evidence you supplied. Do not invent a date, edit a statement or describe someone else's funds as your own. Inconsistent explanations can prolong the review and create a separate integrity problem.

The note should also state how you obtained each document. A downloaded platform CSV, an official bank PDF and a screenshot have different evidential value. Where a screenshot is the only available record, preserve the wider screen context and ask whether the reviewer needs another format.

What if the exchange asks for more documents or rejects the submission?

Read the response as a list of unresolved links. Ask support to identify the transaction, field or time period still unsupported. A useful follow-up question is: “Which claimed step cannot be verified from the documents supplied, and what document types are accepted for that step?”

Keep every message and submission receipt. Reply within the stated deadline or request an extension before it expires. If staff give contradictory instructions, refer to the case number and ask for one consolidated written requirement. Do not repeatedly upload different versions without an index; that makes comparison harder.

If the exchange declines the evidence, request the reason it can disclose, the policy governing reconsideration and the formal complaint or appeal route. A restricted account may have separate withdrawal or account-closure procedures. Those procedures are distinct from proving source of funds and should be handled under the platform's published terms, not through strangers offering paid “unlocking” services.

A final checklist before submission

The request is visible or confirmed in an authenticated official channel.
The case scope, deadline, formats and permitted redactions are clear.
Every relevant deposit maps backwards to an identifiable origin.
Names, dates, assets, amounts, fees, addresses and transaction IDs reconcile.
Originals are preserved and submitted copies have not been misleadingly altered.
Unrelated sensitive information is minimized without breaking the evidence chain.
Missing records and estimates are labeled rather than concealed.
The cover note maps each claim to a numbered attachment.
A local copy of the package and submission receipt is stored securely.

Frequently asked questions

Does a source-of-funds request mean the exchange thinks I committed a crime?

No. It means the exchange wants evidence to understand activity under its compliance process. A trigger can be routine or risk-based. Only the exchange can explain the scope of its review, and a request alone does not establish wrongdoing.

Is a blockchain transaction hash enough proof?

Usually not by itself. A hash can show that assets moved between addresses, but it does not necessarily show who controlled them, how the assets were acquired or why the transfer occurred. Pair it with account and origin records.

Can I redact my bank statement?

Only within the exchange's instructions. Redacting unrelated purchases may be acceptable, but hiding ownership, relevant dates, amounts, counterparties or the transfer path can make the evidence unusable. Ask before redacting uncertain fields.

Should I send my wallet seed phrase to prove ownership?

Never. A seed phrase or private key gives control of assets and is not an appropriate verification document. Use safer ownership evidence requested through the exchange's official process.

What if the money came from several years of savings?

Explain the accumulation period and ask whether the exchange needs source-of-wealth evidence as well as the immediate source of funds. Provide representative or required records rather than assuming one recent statement proves the full history.

Can a VPN complete or avoid a compliance review?

No. A VPN cannot prove economic origin, replace documents, change platform obligations or guarantee account access. It should not be used to misrepresent location or evade a service's controls.

How long will the review take?

There is no universal timetable. Complexity, missing evidence, provider workload and legal requirements all matter. Track the stated deadline, keep the case reference and use the formal escalation route if updates stop.

Disclaimer: This article provides general security and compliance-record information, not legal, tax or financial advice. Document requirements and review rights vary by provider and jurisdiction.

If you upload bank statements or payslips for a source-of-funds review over hotel or café Wi-Fi, AethoVPN can encrypt the hop between your device and its server, but it does not decide which documents the exchange accepts or who can read the files after upload.

Sources

［1］FATF — Virtual Assets Red Flag Indicators of Money Laundering and Terrorist Financing: https://www.fatf-gafi.org/content/dam/fatf-gafi/brochures/Handout-Red-Flags-VA-Financial-Non-Financial.pdf

［2］European Banking Authority — Guidance to crypto-asset service providers on money-laundering and terrorist-financing risks: https://eba.europa.eu/publications-and-media/press-releases/eba-issues-guidance-crypto-asset-service-providers

［3］EUR-Lex — Directive (EU) 2015/849, consolidated text: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02015L0849-20241230

Sources checked 6 September 2026.

Related articles:

Crypto Exchange Requests Source-of-Funds Documents