Wrong Address Payment

Overview

Wrong-address payments can result from copying mistakes, address poisoning, clipboard malware, reused payment instructions, or selecting a destination from the wrong contact or network. A checksum may catch some typing errors, but a valid malicious address passes normal format checks.

The first response is to preserve transaction details: network, asset, hash, destination, amount, block, and time. The sender should contact the destination owner or service when identifiable. Exchanges and custodians may recover funds sent to an address they control, but they can require proof, fees, and manual processing.

Sending to a valid address on the wrong blockchain is a related but different problem. Recovery depends on whether the destination key is controlled on both networks and whether the asset contract supports retrieval.

Businesses should reduce risk through invoice-specific QR codes, full-address verification, trusted address books, network-aware validation, and cooling periods for new payout destinations. High-value transfers can use a small test transaction when operationally appropriate.

Support teams should never request seed phrases or private keys. They should also avoid promising recovery before confirming control and technical feasibility.

A wrong address payment is valid protocol execution with incorrect business intent. Prevention is more reliable than post-settlement recovery.

Payout systems should treat a newly added destination as a high-risk configuration change. Strong authentication, delayed activation, and notifications reduce account-takeover loss. Address books should store the full chain and asset context, not one string reused across compatible-looking networks. Periodic re-verification is important for exchange deposit addresses, which can change or require new memos.