Before sending, compare the receiving instructions with the final transfer preview: exact asset, network, address, memo if required, and net amount. Verify the details after pasting and again before signing. A valid address format does not prove that the receiving service supports the selected route.
Create one authoritative set of receiving details
Open the recipient's actual Receive or Deposit page. If sending to another person, ask them to obtain the instructions from that page rather than forwarding an old address from transaction history. Establish the asset and network together.
Keep the instructions as one set. An address from one conversation, a network from another, and a memo from an old screenshot can produce an invalid combination even when each item once belonged to the same recipient.
Where a platform provides a memo or tag, treat it as part of the destination. It can allow a shared deposit address to be associated with the correct customer. Omitting it can leave the transfer visible on-chain without a corresponding customer credit.
Ask for clarification if the receiving page does not name the network you intend to use. Do not translate uncertainty into a guess based on the cheapest option, a familiar abbreviation, or the appearance of the address.
For an address generated by a hardware wallet, use the supported device display to verify it. A computer's receive screen and a device-confirmed address should agree before you ask a sender to use the destination.
Catch errors introduced during entry
Select the asset and network deliberately in the sending interface. If changing one field refreshes or clears another, review the entire form again. Some interfaces infer a network from the address, but that inference cannot establish the recipient's deposit policy.
Paste the address from the verified source and compare the complete result. Malware, address-history manipulation, or an ordinary copy mistake can substitute a different value. Checking only a few characters may miss a carefully similar address.
Read QR-code results rather than assuming every scan contains the same information. Depending on the format and application, a code can populate an address and other fields. Inspect what actually appeared in the transfer form.
Check amount units and memo placement. A number entered as a memo is different from the transfer quantity, and a fiat-valued amount can change with a quote. Read each label before moving forward.
If you are interrupted, start the comparison again from the final preview. Memory of a check before the interruption is weaker than inspecting the instruction that is actually about to be signed.
Use a read-back immediately before confirmation
- Name the asset you are sending and verify its contract or representation where the receiving instructions specify one.
- Read the full network name in the sender's preview and compare it with the recipient's current support. Do not rely only on a token-standard abbreviation.
- Compare the destination address and any required memo with the original instructions. If anything differs, stop before authorizing.
- Check the net delivery against the destination's requirements. A small amount below a credit threshold is not a valid test of ordinary receipt.
- Review warnings and any beneficiary information requested by the provider. Resolve a mismatch rather than clicking through it.
- After submission, preserve the network, withdrawal reference, and transaction hash. Verify actual receipt before treating the route as established.
What a test transfer can and cannot establish
A test can show that one specified asset reached one destination through one route at that time. It helps detect misunderstandings before a larger amount is exposed. Use a test that satisfies the sender's and receiver's minimums.
Wait for the intended outcome. For a personal wallet, confirm the correct asset in the correct account and chain. For an exchange, verify the customer's deposit credit rather than merely a successful public transaction.
Review the main transfer independently. An address can be changed, a clipboard entry overwritten, or a network reset between operations. A successful test does not validate a different final preview.
Remember the extra cost. A test is a verification measure with its own fee, not a guarantee that the total route becomes cheaper. If a provider imposes fixed charges per request, include both requests in the budget.
A test cannot prove that a contract's permissions will remain unchanged or that a service will always support the route. Refresh instructions when using it again after a support change, account change, or significant delay.
If you notice an error after sending
Check whether the request is still internal to the sending service, broadcast but unconfirmed, or already confirmed. Follow the service's documented cancellation process if one exists. A cancellation request is not a promise that processing will stop.
Once a transfer is confirmed, editing the saved address does not change the completed instruction. Preserve the actual network, hash, asset, quantity, and destination. Those facts are the starting point for determining who can help.
If the destination is a custodial platform, contact its official support about the exact route received. Recovery depends on asset support, network access, technical controls, and the provider's process. Do not assume the sending exchange can credit another company's customer account.
If the destination is a self-custody account you control, establish the type of account and network support before following recovery advice. The same-looking address on another EVM network may have a different contract deployment or access situation.
Stop repeating the transfer while the issue is unresolved. An additional payment can create another unsupported deposit and another fee. Do not send recovery phrases or private keys to someone offering to investigate a public hash.
After the case is understood, update the receiving instructions and remove misleading saved entries where appropriate. Record the specific failure point, such as an old network label or a missing memo, so your next check addresses the actual cause.
For recurring payments, keep an address-book entry that names the asset, network, recipient, and purpose together. Review it when the recipient changes platforms or updates deposit instructions. A saved entry should help locate the correct details, while the current receiving page confirms they remain valid. If several people approve a transfer, agree which person obtains the instructions and which person performs the final comparison. Clear responsibility is more useful than several people each assuming someone else checked the network. Keep the final submitted instruction with the receipt so the team can later distinguish an entry mistake from a processing issue.
Reader questions
Does choosing an inexpensive network automatically bridge the asset?
No. The selected withdrawal network determines the transfer route. Bridging requires an appropriate separate mechanism.
Can the correct address compensate for a missing memo?
A custodial service may need both to allocate the deposit. Use its official process if the memo was omitted.
Should I trust a new address sent by someone claiming to be support?
Verify the request through the provider's authenticated support channel before making any further transfer.