Wrong network or wrong address: what to do next

The idea in plain English

First stop sending additional funds and record the transaction reference, network, asset identifier, destination and any memo. Check what actually happened on the relevant network. A wrong-address transfer, wrong-network deposit and delayed provider credit are different problems with different possible outcomes.

The distinction that matters

For a custodial receiver, contact official support through an independently verified route and read its unsupported-deposit policy. Only the party with the necessary control may be able to help, and recovery may be impossible. For self-custody, network compatibility can be complex; do not import your phrase into a suggested rescue site.

A practical example

A deposit goes to an exchange address on a network the exchange does not support. The visible address may look familiar, but only the exchange can explain whether it controls the relevant keys and offers recovery. A stranger cannot prove that by showing a polished recovery dashboard.

Try this without moving money

• Collect non-secret transaction facts and compare intended versus actual fields.
• Use the receiving service’s verified support process when relevant.
• Keep records and stop any conversation asking for a recovery phrase or advance rescue payment.

A mistake to avoid

Do not assume a blockchain transaction has a central cancel button. Additional payments can compound the original loss.

Before you act

Matching an address format is not enough. The receiving service must support the exact asset and network, and any required memo or tag. Fees, minimum deposits and confirmation policies can change. The practice exercises here are simulations: they neither validate a real address nor send a transaction.