Before you send crypto, check more than the address

An address alone is not a complete transfer instruction. Before sending crypto, confirm that the receiving service supports the exact asset on the exact network, and whether it needs an extra reference.

The coin name is only the beginning

A network is the system on which a transfer is recorded. An asset with a familiar ticker may be available on several networks. A receiving platform may support some routes but not others. Coinbase’s multi-network guidance tells users to check that both ends use the same network.

Use the receiving platform’s current deposit screen and documentation. Do not pick a network just because its displayed fee is lower. A cheaper unsupported route can be a much more expensive mistake.

Compare exact asset names and any contract identifiers the service provides. This guide does not supply an address or a supported-network list because support can change. Old screenshots and another person’s previous successful transfer are insufficient evidence for your current route.

The small field that can matter

Some deposits need a memo or destination tag: an additional reference used to assign a shared receiving address to the correct customer. The receiving platform determines whether it is required. Coinbase warns that omissions or mistakes can cause delay or loss.

Copying an address does not necessarily copy this reference. Check the full receiving instructions together. Do not replace a required reference with your name or a made-up number.

A five-point pause before confirmation

1. Recipient: did you obtain the instructions from the intended person or service through a verified route?
2. Asset: is it the exact supported token, not merely a matching ticker?
3. Network: does the receiving platform explicitly support this deposit route?
4. Address and reference: do the complete details match the receiving instructions?
5. Amount and cost: do minimum deposit rules and all fees leave a usable amount?

A small test can help reveal a mistake where practical, but it still costs money and may be below a deposit minimum. Check those constraints first. Receiving one test successfully is not a guarantee against later errors, changed support or fraud.

After sending, keep evidence

Keep the transaction reference, time, asset, network and amount privately. Distinguish a transfer recorded on the network from a deposit credited to a service account. If credit is delayed, use the receiving service’s official support process; do not pay an unsolicited “fixer.”

Crypto payments generally cannot be recalled like a normal card dispute. A recipient returning funds is different from a guaranteed reversal mechanism. Recovery possibilities depend on the route and circumstances.

Your next action

Save a transfer checklist beside the official receiving instructions before entering the sending screen. Stop if any field is unsupported, ambiguous or supplied only by an unsolicited contact.

Sources and review

Checked 12 October 2026. Source dates describe the underlying publications, not new events today. Provider documentation describes stated terms and does not prove safety or suitability.

• Coinbase: assets on multiple networks — No publication date displayed; Provider example only; some legacy token references excluded.
• Coinbase: destination tags and memos — No publication date displayed; Provider example; receiving platform determines requirements.
• FTC: cryptocurrency scams — May 2022; U.S. consumer guidance.

General education, not a recommendation to buy, sell or use a provider. Crypto can lose value; access, fees and legal treatment vary. We review changing provider and legal details monthly, security fundamentals quarterly, and material known changes sooner. Material corrections are dated on the page.