Proving the source of crypto funds to a bank involves more than showing a wallet screenshot. The file should explain how the money was obtained, invested, transferred and eventually sold. A payment received from a platform identifies one stage of the journey; it does not necessarily establish the funds’ economic origin or provide their complete history.
This guide sets out a documentary approach, primarily for discussions with a bank in France. It is neither a universal list of mandatory documents nor a guarantee that a transfer will be accepted. Requirements depend on the transaction and the circumstances. The right approach is to explain the facts with consistent documentation—not to circumvent controls or manufacture an appearance of simplicity.
In brief
- The immediate source of a transfer and the economic origin of the capital answer two different questions.
- Bank statements, exchange exports and blockchain transactions should connect without counting the same funds twice.
- No supporting document requires you to disclose a seed phrase, private key or access that could be used to move the funds.
Proving the source of crypto funds starts before the sale
A crypto exit plan should account for documentation as well as prices. Waiting until a large transfer prompts a request leaves less time to retrieve an old account, statement or export. Preparing the file while access is still available reduces reliance on a provider’s archives several years later.
In France, the joint guidelines issued by the ACPR and Tracfin, in the version published in 2025, notably distinguish between the source of funds and their economic origin. They explain that documentation showing a transfer is not always enough to clarify the transaction. This framework does not establish a standard list of crypto documents applicable to every customer.
The process should therefore begin with a factual timeline. When was the initial capital obtained? Through which account did it reach the platform? What transactions led to the assets that were sold? Where should the sale proceeds arrive? Answering these questions in order helps build an intelligible file without confusing proof of a deposit with an explanation of wealth.
Funds originating from saved wages, a property sale or an inheritance call for different source documents. The records must reflect the individual’s actual circumstances. A template can organize the material, but it must never provide a story to copy in place of missing evidence or conceal a poorly understood transaction.
Building a chain from initial capital to the final transfer
Consider an entirely fictional example: €5,000 in bank savings is sent to an exchange, used to buy assets, and those assets then pass through a personal wallet before a later sale for €8,000. The statement for the final transfer proves only that the €8,000 was received. Explaining the journey requires linking each intermediate step.
The file may include the statement from the originating account, confirmation of the exchange deposit, the purchase history, the withdrawal to the wallet and the return of the assets to a selling platform. Identifiers make it possible to connect the transactions. Amounts will not always match because of fees and changes in quantity; those differences should be explained.
The BrefCrypto glossary helps distinguish between an address, a transaction and a platform account. A public address does not, by itself, prove the civil identity of its holder. Conversely, an exchange’s internal identifier is not necessarily a blockchain hash. Documents should clarify the nature of each reference rather than presenting them as interchangeable forms of proof.
Continuity does not mean burying the recipient under thousands of unexplained lines. A short summary can refer to numbered annexes. The reader should be able to start with the final amount and trace it back to the initial capital, significant transactions and fees without having to guess why a particular transaction was included.
Preparing readable documents without overstating what they show
Original files exported from a platform serve a different purpose from screenshots. A CSV facilitates calculations and reconciliation, while a PDF or named account statement may document the account and period. Keeping both formats, when available, avoids relying solely on a manually altered spreadsheet or a partial image.
An export should be opened and checked. The date range, time zone, currency, transaction type and pagination can affect what it contains. A file called “transactions” may exclude certain movements or show only part of the products used. A reassuring report name does not guarantee that it covers the entire journey being explained.
Changes made to improve readability should remain traceable. Keeping the original intact, preparing a working copy and documenting any conversions makes it possible to distinguish source data from analysis. A statement should never be rewritten to make two amounts match artificially. An explained discrepancy is better than a perfectly balanced but unverifiable table.
Relevant tax documents may supplement the file without replacing economic evidence. A tax return does not necessarily prove every transfer, and a blockchain transaction does not settle reporting obligations. When the transaction history is particularly complex, a qualified professional may help reconstruct it, without guaranteeing the bank’s final decision.
Handling personal transfers, DeFi and P2P transactions
Moving assets between two personal wallets does not automatically create a new investment or economic income. The file should identify the movement as an internal transfer and connect both ends. A multi-wallet setup can strengthen certain security controls, but it also increases the number of accounts and addresses that must be catalogued to understand the overall journey.
A bridge or DeFi protocol adds steps that cannot always be read as a simple transfer. The guide to bridges helps identify the network change and the assets received. For the file, explain the mechanism actually used, including its contracts and transactions, without describing every token received as a profit.
P2P trades require their own supporting documents: the order, the agreed terms, the identity available through the service and relevant proof of payment. The information retained must comply with applicable rules and protect third-party privacy. An isolated message or pseudonym may not be enough to explain the economic origin of a substantial amount.
When a document is missing, it is better to identify the gap and look for an honest substitute source. Platform support, an old statement, a confirmation email and public data may help reconstruct the history. No analytical tool should turn a presumed match into conclusive evidence without preserving the limitation and the elements on which it is based.
Submitting the file without exposing your secrets
Supporting documents should be sent through an authenticated channel confirmed directly with the bank. A request received by private message, an unfamiliar link or a pressured phone call should be verified separately. The fact that someone knows the amount of a transfer is not enough to prove that they represent the institution or its compliance department.
A seed phrase can potentially control the assets in question. The method for backing up recovery keys concerns their protection, not their use as evidence. Do not disclose these words, a private key or an API key that enables withdrawals to prove ownership of a wallet.
A signature requested on a blockchain also deserves careful scrutiny. Some signatures can authorize actions rather than merely demonstrate control. Do not sign an opaque message or unknown transaction under pressure. If a specific proof of control appears necessary, clarify its purpose and format with an authenticated contact before taking any action.
Documents may contain sensitive information about assets and counterparties. Limiting copies, using protected storage and checking recipients reduces the risks. A redacted summary can be used for an initial exchange, but redactions must not remove information needed for analysis or create a misleading representation of the transaction.
Answering questions without inventing a magic threshold
Under this approach, no amount guarantees that questions will not be asked. Artificially splitting a transfer to avoid scrutiny does not eliminate the need for documentation and may make the transaction history harder to understand. The right approach is to present the facts, timeline and documents without looking for a combination supposedly designed to neutralize controls.
If additional information is requested, asking which part of the transaction requires clarification makes it possible to respond more precisely. A tracking table can record the documents sent, dates and outstanding questions. Keep a copy of the correspondence and distinguish between a request for information, a processing delay and a formal decision, which do not carry the same significance.
If disagreement persists, use the institution’s complaints channels and seek advice suited to the circumstances. No standard file guarantees that a bank will accept a particular transaction. This guide does not determine a customer’s individual rights in response to a decision; legal analysis may be necessary when the stakes or dispute warrant it.
The most useful file ultimately tells a simple story because it rests on evidence, not because it erases complex steps. The initial capital, transactions, holdings and sale should connect. This discipline makes discussions with the bank easier while improving wealth tracking, without requiring any alteration of the facts or compromising the security of the funds.