How to Check a Crypto Address Before Sending

Before confirming a crypto transfer, check four things on the final wallet screen: the recipient address, the asset, the network and any required memo or tag. If even one does not match the recipient’s instructions, stop. A correctly formatted address can still belong to the wrong person or be incompatible with the network you chose.

Use this pre-send checklist:

• Recipient: Compare the address with one obtained directly from the intended recipient or their official app.
• Asset: Confirm the exact coin or token, not just a similar ticker or name.
• Network: Match the sending and receiving networks exactly.
• Extra details: Include a required memo, destination tag or payment reference.
• Amount and fees: Check the amount the recipient should receive and the fee charged by your wallet.

Crypto transfers are usually difficult or impossible to reverse once confirmed. Take the time to check before you approve; speed is less important than matching every detail.

Start by confirming that the receiving wallet or platform supports the asset on the network you plan to use. A token may be available on several networks, but those versions are not automatically interchangeable. Sending an asset over an unsupported network can leave it inaccessible, even if the address looks familiar.

Ask the recipient to specify both the asset and network. Then compare that with the network selected in your sending wallet. For example, do not assume that choosing a token with the right name also chooses the right chain. If the recipient is an exchange, use its deposit instructions for that exact asset and follow any network restrictions it lists.

Before proceeding, check:

1. The asset name and ticker are the intended ones.
2. The network name matches on both sides.
3. The receiving service accepts deposits on that network.
4. The amount meets any stated minimum deposit.

If the instructions are unclear, ask the recipient or platform to confirm them through an official support channel. Do not guess based on an address format or a previous transfer.

Get the destination address from a trusted, current source: ideally the recipient’s wallet or the deposit screen of the service you are using. Avoid relying on an old message, saved screenshot or address found in a search result. If someone sends a new address unexpectedly, verify the change through a separate channel you already trust, such as a known phone number.

After copying the address, paste it into your wallet’s recipient field and compare it with the original. Check the first and last several characters, then inspect the full address if your wallet allows it. Do not assume a brief matching prefix and suffix proves that every character is correct.

Clipboard malware can replace a copied address with one controlled by a scammer. To reduce the risk:

• Recheck the address after pasting, not just before copying.
• Do not copy an address from an unfamiliar pop-up or unsolicited message.
• If you scan a QR code, verify the decoded address shown in your wallet.
• For a large transfer, confirm the destination directly with the recipient before sending.

A QR code is a convenient way to enter an address, not proof that the address is genuine.

Check the address as a complete string. Wallets may flag an invalid format or display a checksum warning, but passing that check only means the address appears structurally valid. It does not establish who controls it or whether it belongs to your intended recipient.

Be especially careful with address poisoning. A scammer may send a tiny transaction from an address that resembles one you used before, hoping you will copy it from your transaction history. Similar-looking addresses are not interchangeable. For a new transfer, obtain the destination from the recipient’s trusted instructions rather than selecting a lookalike from recent activity.

If you use a human-readable name or domain instead of a long address, verify the name carefully and check the resolved address shown by your wallet. Names can be mistyped, imitated or point somewhere unexpected. Do not approve if the wallet cannot show you the destination or if the resolved address differs from the one the recipient confirmed.

An address checker or blockchain explorer may help you inspect public transaction history, but it cannot certify that the address is safe or owned by a particular person. Treat such tools as additional context, not a substitute for confirming the recipient.

Some networks and services require an additional destination detail, such as a memo, tag or payment reference. It helps the receiving service identify which customer should be credited when many users share a deposit address. Leaving it out or entering it incorrectly can delay a deposit or require the service to investigate it.

Read the receiving platform’s deposit instructions for the exact asset and network. If a memo or tag is shown as required, copy it into the corresponding field in your sending wallet and check it before confirming. Do not put the memo into the address field, and do not assume a tag from an earlier deposit is still correct.

Use this final check for exchange deposits:

• The address matches the platform’s current deposit screen.
• The selected network is supported for that asset.
• The memo or tag is included exactly as displayed, if required.
• The destination has not changed since you copied it.

If the sending wallet has no field for a required tag, stop and contact the wallet or platform through its official support route. Do not send first in the hope that the service will identify the payment automatically.

For a new recipient, a small test transfer can reduce the amount at risk. First check whether the wallet or service accepts small deposits and whether a minimum applies. A test is not free: you may pay a network fee, and an exchange may have deposit or withdrawal rules that affect the amount credited.

After sending the test, wait until it appears in the recipient’s wallet or account and confirm with the recipient that it arrived. Check the transaction status and destination on a reputable explorer for the correct network if you need to investigate a delay. An explorer can show whether a transaction was broadcast and confirmed, but it cannot make an unsupported deposit recoverable.

Before sending the remainder, repeat the address, network, asset and memo checks. Do not rely on the test transaction in your history without checking its full destination: address-poisoning scams can exploit transaction lists. For a familiar, previously verified recipient, you may decide a test is not worth the extra fee, but never skip the core checks.

Network fees vary with the chain and its current conditions. Your wallet should show an estimated fee before approval; check that the amount and fee are acceptable, and leave enough of the network’s native token if the wallet requires it to pay for the transaction.

A common mistake is checking only the first few characters of an address. Scammers can create lookalikes, and a familiar-looking address is not enough to identify its owner. Compare the full destination or use your wallet’s complete-address view before approval.

Avoid these other shortcuts:

• Assuming matching address formats mean matching networks. Confirm the network on both sides.
• Trusting a message that changes payment details. Verify unexpected changes through a separate, known channel.
• Ignoring a warning or missing tag. Stop and resolve it before sending.
• Rushing because a recipient says it is urgent. Urgency is not a reason to bypass checks.
• Believing a checker guarantees safety. A tool can flag issues but cannot prove who controls an address.

If a detail does not match, cancel or leave the transaction unapproved and ask for fresh instructions. Never share your recovery phrase or private key to “verify” an address; a legitimate recipient does not need either to receive a payment. Be wary of anyone demanding an extra payment to unlock, reverse or recover a transfer.

After approval, save the transaction ID and check the transaction status on the correct network if the recipient does not see the funds. Confirm that the destination, asset, network and amount in the transaction details match what you intended. A pending transaction may take time to confirm; sending it again before checking its status could create a duplicate payment.

If the transaction is confirmed but the recipient cannot find it, contact the receiving service through its official support channel. Provide the transaction ID and relevant details, but never your recovery phrase or private key. If you sent to the wrong address or network, contact the recipient or the service that controls the destination as soon as possible. Recovery is not guaranteed and may be impossible.

Keep a record of verified recipient details only if you can protect it and know when to refresh it. Deposit addresses, tags and network support can change, especially at custodial services. For the next transfer, check the current deposit screen again rather than treating an old record as permanently valid.

The safest habit is simple: verify the instructions, inspect the final wallet screen, and approve only when every detail agrees.