AML Review of Transfers Between Your Own Wallets: What to Prove

When an AML review concerns transfers between your own wallets, show the relevant path and distinguish address control from the source of the assets. A signature can support control of a particular address, while transaction records show movements and acquisition records explain where the value came from. Saying both wallets are mine does not make those different questions disappear.

Start with the reviewer’s missing link

Read the request against the transaction being reviewed. Is the service asking who sent the deposit, whether you control a destination, how an earlier withdrawal relates to it, or how you acquired the assets? Write that question beside the relevant transfer. Do not respond to a request about the original purchase only with proof that you can access the most recent wallet.

Coinbase’s account-review guidance describes requests for exchange records, wallet history and information connecting assets across accounts. It also distinguishes the source of funds from the immediate transfer path. Those are examples of one platform’s review process, not a universal requirement that every wallet holder must submit the same file.

Use a fictional route to see the distinction: Omar buys an asset on an exchange, withdraws to wallet A, moves part to wallet B and deposits that part into another service. The last deposit proves a movement from B. It does not alone establish the earlier exchange purchase, the A-to-B relationship or the person controlling either address. Each missing link needs the appropriate record rather than a broader assertion of ownership.

Map the route without turning every address into a personal identity

Keep the account relationship and the chain transaction side by side. A custodial exchange can send a withdrawal from its own operational wallet. Your account’s withdrawal record may connect you to that payment, but it does not give you the private key for the exchange’s sender address. If asked to sign for an address you never controlled, explain the custodial step instead of trying another wallet or obtaining a secret from a supposed helper.

For each movement, preserve the network and asset identity as well as the amount and time. A conversion or bridge may produce distinct source and destination records, and fees or partial transfers can prevent identical amounts. Mark those transitions and use their actual records. Do not present two similar amounts as proof of a relationship when the connecting step is still missing.

Ask what the proposed ownership proof actually proves

A dedicated verification message is different from an onchain test payment. Kraken’s signature-verification page describes a unique, non-transactional message for confirming address control. That description concerns its intended verification flow. It is not a reason to approve any wallet request displaying a familiar name or to assume that every signature shown by another website has the same scope.

The BitBox control-proof guide distinguishes accepted message formats, AOPP and a Satoshi test. It also explains their limits: demonstrating control of an address is not the same as establishing identity, legal ownership or control of every address. Match the requested method and address to the service’s current instructions before deciding whether your wallet can perform it.

A screenshot is useful context but is not equivalent to an accepted cryptographic proof. Conversely, a valid control proof does not explain an inheritance, business sale or earlier purchase. If the reviewer has asked for both control and origin, treat them as two evidence tasks. Neither should be labelled completed merely because the other produced a successful result.

A test payment is a separate action with a separate cost

Coinbase’s EU customer transfer page describes a small-deposit test among its methods. Unlike a non-transactional message, it transfers funds and can incur network costs. This is a provider-specific example, not a recommendation to send test payments whenever somebody claims verification is needed or a statement that the same procedure applies everywhere.

If such a test is actually requested in an authenticated workflow, establish the required source, destination, asset, network, amount and completion conditions. If the wallet cannot satisfy the specified method, ask the service about an accepted alternative. Do not improvise a preliminary transfer or pay an external verification agent. The test’s completion also does not automatically settle a separate source-of-funds review.

Bitcoin creates an additional scope question because one wallet can use several addresses. A proof tied to one address is not automatically proof for every other receiving or change address. Keep that distinction explicit rather than declaring the whole wallet verified. If a service offers a broader public-key-based method, understand what related address activity it would disclose before sharing those wallet-wide records.

Prepare a focused reply, not a new history

1. Identify the particular gap in the review and the transaction it concerns.
2. Map only the relevant acquisition, withdrawal and wallet movements in chronological order.
3. Attach original provider records to the steps they actually support.
4. Explain custodial sender addresses, conversions, partial amounts and missing records accurately.
5. If address control is requested, confirm the accepted method, format and scope through the service’s official process.
6. Retain the submitted explanation and ask which link remains unresolved if further evidence is needed.

Keep real records unchanged and describe unavailable evidence honestly. A personal movement does not become a new acquisition event simply because it reaches a fresh address. Do not relabel a gift, third-party payment or custodial withdrawal as a transfer from a private key you personally control. A clear explanation can be incomplete; it should not be made falsely complete for the sake of a tidy table.

Send evidence only to the intended reviewer through its established channel. An address, signed message or transaction can connect your identity to chain activity even without revealing a spending secret. Review the requested scope and never disclose recovery phrases or private keys. The goal is to answer a concrete question with suitable evidence, not to provide open-ended access to every account you have used.

Keep the destination service’s decision separate

KOT.CASH’s AML policy permits risk-based requests for source or identity information. A chain of transfers between your own wallets does not remove that review. When asking about a simple swap, retain its order reference with the relevant transfer records and consult how the service works. No-account exchange can still pause suspicious activity, and this evidence map promises neither approval nor a completion deadline.