How to Send Crypto Safely: Network, Address, and Memo Checks

A ticker such as ETH, USDC, or USDT is not a complete transfer instruction. An asset can exist on several networks, and the same name or ticker can refer to different token contracts. Before sending, confirm the asset, the network, and the exact destination the receiving service gave you.

The Ethereum.org wallet guide notes that assets such as DAI and USDC can exist on multiple networks and are not interchangeable just because they share a name. Treat the network as part of the destination details. If an exchange shows a deposit network, use that exact option rather than choosing the network that looks familiar or has the lowest fee.

Also distinguish a wallet address from an exchange account destination. A self-custody wallet may show a blockchain address you control; a custodial platform may provide a deposit address plus a memo, tag, or other account identifier. Read the receiving instructions for the specific asset and account each time.

Open the receiving wallet or exchange first and select the asset you plan to receive. Check the supported network and copy the address generated for that exact choice. Then return to the sending side and select the same asset and network before pasting the address.

Some EVM-compatible networks can use the same address format, and a wallet may show the same account address on more than one network. The network still has separate balances and transaction history. Sending a token on a chain the recipient does not support may leave the recipient unable to credit or access it, even when the address characters look correct. Ethereum.org describes the need for sender and recipient to use the same network for a transfer.

Do not infer network support from a matching address prefix, a familiar token logo, or a network name in a search result. Check the recipient's current deposit page or wallet documentation. Supported assets and networks can change, so a saved address alone is not enough.

For some chains, the address is only part of the destination. A custodial service may use one shared on-chain address for many customers and rely on an additional memo or tag to assign an incoming payment to the right account. On the XRP Ledger, a destination tag can identify which customer should be credited. Stellar services may use a memo or muxed address for similar routing.

Enter the identifier exactly as the receiving service displays it, and use the field the sender provides for that purpose. Do not add a tag to an unrelated chain or invent one when none is requested. A memo is not a substitute for the address or the network; the transfer still needs the correct asset and destination address.

If the recipient gives you a combined address format, use it as instructed. Some formats encode an identifier with the address; others require two separate fields. The exact requirement depends on the chain and the receiving service. XRP Ledger and Stellar documentation explain these designs, while the receiving platform tells you which one applies to your account.

A direct transfer moves an asset on the selected blockchain to an address on that network. A bridge is a separate protocol workflow for moving value or a representation of an asset between networks. It can involve a source-chain transaction, a destination-chain transaction, fees, waiting, and a route-specific asset representation. A wallet network switch by itself does not bridge funds.

Coinbase’s send instructions illustrate the details to review for an on-chain send. Some exchanges also offer internal sends between customers on the same platform. Those may update the platform's own account records without creating the same kind of public on-chain transfer. Check whether the send screen says on-chain or internal, and make sure the recipient can receive that route.

When using a bridge, verify the source network, destination network, asset received, amount after fees, expected wait, and the official bridge interface. Ethereum.org's bridge guide treats bridging as its own process, with a separate wallet connection and transaction review. Do not send to an address from a different route just because the token ticker matches.

For a new destination or a large transfer, a small test can reveal a copied-address, network, or memo mistake before you send more. If the test arrives and is credited to the right account, repeat the same route only after checking the details again. A successful test does not guarantee that a later transfer will use the same network or destination settings unless you verify them again.

Check the receiving service's minimum deposit before choosing a test amount. A test below the minimum may appear on-chain but not be credited automatically. Each test can also incur a network fee, and a required memo or tag still has to be included. There is no universal test amount that works for every token, chain, or exchange. Coinbase’s memo and destination-tag guidance recommends a small test in certain deposit situations; follow the receiving service’s specific instructions.

Use the exact deposit instructions shown for the receiving account. If the service says a small test is unsuitable or gives a minimum, follow that guidance. Never treat a test as proof that a different token contract, network, or account will work.

Before confirming, compare the asset and network, destination address, memo or tag, amount, and fee with the receiving instructions. Check the entire address where possible; matching only the first and last characters can miss an error in the middle. Reopen the receiving screen if you are unsure which network or identifier applies.

Start from the official wallet or exchange app, not a support message, advertisement, or direct-message link. Clipboard replacement malware can alter a copied address, so verify the pasted destination on the final confirmation screen. For a bridge, review both the source and destination networks and the token you expect to receive.

A hardware wallet can help protect private keys and show transaction details, but it cannot decide whether the chosen network or destination is correct. Do not sign a transaction you cannot understand. A legitimate support agent should not need your seed phrase or private key to check a transaction hash.

After an on-chain send, save the transaction hash and look it up on the correct network's block explorer. Confirm the destination, asset, amount, and transaction status. A transaction marked successful on-chain shows what happened on that chain; it does not by itself prove that a custodial platform has credited your internal balance.

The receiving service may wait for a required number of confirmations, apply a minimum deposit, or review a missing memo or unsupported network. Kraken’s missing-deposit checklist covers these checks. Processing times can vary with network conditions and platform status. Compare the transaction details with the receiving service's current deposit rules before sending a second payment.

If the wallet shows a pending transaction, inspect its status before trying again. A second send can create a second payment rather than fix the first one. Ethereum.org recommends using a block explorer to check a transaction ID or address; exchange support pages provide separate checks for account credit and missing deposits.

Do not send another transaction to try to repair the first one. Save the transaction hash, source network, asset, amount, destination address, memo or tag, and approximate time. Check the transaction on the source network's explorer, then use the receiving platform's official support or recovery process.

A wrong-network transfer may sometimes be technically accessible if the recipient controls the relevant keys and supports that chain and token. If the destination is a custodial platform, a shared address, or an unsupported network, the recipient may not be able to recover or credit it. A missing or incorrect tag can also leave a confirmed payment without an automatic account match. Recovery depends on the specific destination and is not guaranteed; Kraken’s recovery guidance describes these limitations.

Do not share a recovery phrase, private key, or wallet password with anyone offering to recover funds. Use only support channels reached from the recipient's official website or app, and be cautious of people who ask for an upfront payment or request a new signature unrelated to the case.

1. Open the recipient's official app or wallet and select the exact asset and network.
2. Copy the destination address from that screen and verify it again on the sender's confirmation page.
3. Add the required memo, tag, or other identifier in the correct field; confirm whether it is separate or encoded in the address.
4. Check the minimum deposit, amount, fee, and whether this is an on-chain transfer, bridge route, or internal platform send.
5. For a new route or larger amount, consider a small test when the recipient's rules allow it; wait for the right account to receive credit.
6. Save the transaction hash and confirm the status on the correct network before contacting support.

A self-custody wallet gives you control of the signing keys, but it also makes destination checks your responsibility. See the wallet recovery and backup guide for key recovery basics, and the token approval guide for a separate permission you may encounter when using apps. Neither connection permissions nor a hardware signer replace careful transfer details.