To send crypto, obtain the recipient's address and supported network, select the matching asset and network in your wallet, enter the amount, review fees, and confirm. Save the transaction hash and check the result. If the destination requires a memo or tag, include it exactly.

Collect the destination instructions first

Ask the recipient for the asset, network, and address generated by their receiving wallet or platform. If a destination tag or memo is required, obtain that too. A token symbol and an address alone may be insufficient when the asset exists across several networks.

For an exchange destination, use the current deposit instructions for that exact asset. The exchange can impose network, minimum, or transfer-type requirements. The recipient should confirm those details rather than sending you a screenshot whose date and context are unclear.

For a self-custody destination, confirm that the recipient controls the account and can access the network you will use. A wallet application's ability to display multiple chains does not automatically move a token from one chain to another.

If the address arrives through a message, verify it through a trusted conversation with the intended person. When copying it into the wallet, compare the full address. Avoid selecting a similar-looking entry from transaction history merely because its beginning and ending characters seem familiar.

Recipient detailsTransfer reviewReceipt check
Use verified recipient instructions, review the transfer data, and confirm delivery from the transaction record.

Prepare the sending account

Select the account that holds the asset on the intended network. A wallet's combined portfolio value can include several accounts or chains. Inspect the specific balance that will fund this transfer.

Check the network-fee requirement. An ordinary Ethereum token transfer generally needs ETH on Ethereum in addition to the token being sent. Some wallet flows support alternative fee-payment arrangements; use one only when the current interface explicitly offers it for your action.

If sending a network's native asset, leave enough to cover the fee or use a supported maximum-send calculation and review its result. A token balance and a fee balance are separate checks. Changing the displayed fiat currency does not change either requirement.

If the destination has a minimum credit amount, calculate whether the net arrival meets it. Fee deductions at the sending platform or token-specific transfer mechanics can affect that amount. Ask the recipient to verify the receiving rules before testing with an extremely small transfer.

Submit the transfer deliberately

  1. Open Send in the selected wallet account. Choose the correct network and asset before entering the destination.
  2. Paste the verified address and any required memo or tag. If a field you need is unavailable, consult the wallet's supported process rather than sending without it.
  3. Enter the amount in the displayed unit. Check whether the form uses token units or a fiat conversion, and inspect any rounding.
  4. Review the final destination, asset, network, amount, and fee. Read warnings or simulation results. If the destination is a hardware-wallet account, use its supported address-verification procedure.
  5. Confirm only when the details match your intended transfer. Retain the transaction hash once the wallet provides it.
  6. Open the hash on the correct explorer and follow the status. Give the recipient the hash and network so both parties can inspect the same transfer.

Use a test transfer for a new route

A test can establish that the chosen address, asset, and network reached the destination under the current conditions. It is especially useful when a route is unfamiliar. Select an amount that satisfies the sender's and receiver's requirements.

Wait for the recipient to confirm the actual credit, rather than only a submitted notification. An exchange may require additional confirmations before showing an available balance. A self-custody wallet can also take time to refresh its interface.

The main transfer still needs a complete review. Clipboard content, selected networks, and receiving instructions can change between operations. A successful test does not justify skipping the final checks on the larger amount.

Include both transfers in your fee budget. If a fixed withdrawal charge applies per request, the test introduces an additional cost. That cost should be visible when you compare routes, rather than described as a way to make every transfer cheaper.

What to do when the result is unclear

If the transaction remains pending, check whether it was broadcast and whether an earlier transaction from the same account is blocking it. A wallet may offer a supported replacement or speed-up process. Review that process before creating a second ordinary transfer.

If the transaction has failed after execution, inspect the receipt and fee. The intended movement may have been reverted while execution costs remain charged. Investigate the reason before trying again with identical settings.

If it succeeded, inspect the relevant asset movement. On Ethereum, a token transfer can show zero ETH in the main Value field while listing a token movement elsewhere. Read the contract and token-transfer record instead of assuming zero Value means nothing moved.

If the correct address received the correct asset but the recipient does not see it, check their network, account, and display settings. An exchange recipient should also inspect confirmation and crediting requirements. Keep the public evidence separate from the application's display.

A transfer to an unsupported route can require help from the entity controlling the destination. Recovery is situation-dependent. Do not send more funds to the same route to test an unresolved failure, and do not give anyone a recovery phrase to investigate it.

Record the final amount, network, fee, and reference once delivery is understood. These details help both parties reconcile the transfer and give you verified information for future use of the route.

For business or personal bookkeeping, distinguish network delivery from the purpose of the payment. A transfer can reach the stated address while an invoice still needs an internal reference or the recipient needs to associate it with your account. Agree on those requirements before sending. Keep a nonsecret record of the intended recipient, purpose, network, amount, and transaction hash. If a dispute arises, this record explains why that public transfer relates to the obligation you intended to satisfy. Avoid attaching unrelated personal information to public blockchain data merely to make a payment recognizable. Ask the recipient which private confirmation channel they use and supply the relevant identifier there after the transfer.

If the recipient changes instructions, stop and verify the revised destination independently before approving another transfer.

Reader questions

Can I reverse a confirmed transfer by deleting it from my wallet history?

No. Changing a local display does not change the network record. Contact the recipient or relevant platform if an error has occurred.

Can I send to a token's contract address as the recipient?

Use the receiving address supplied for the intended account. A token's contract identifies the asset and is not a substitute for a normal receiving address.

Does the recipient need to keep the wallet app open?

An ordinary on-chain transfer does not require the receiving app to remain open. The app reads the resulting network state when it updates.

Sources and further reading