Sent on the Wrong Network? What Can Be Recovered — and What Can't
The single most common swap mistake. A field guide to what's fixable.
Wrong-network sends are the most common way funds get stuck in a swap. The good news: most situations are recoverable. The bad news: not all. Here's the honest breakdown.
Usually recoverable: sending USDT on a network the order didn't expect (e.g. TRC20 instead of ERC20). The coins are not lost — they're just sitting on a chain the order wasn't watching. Support can locate the transaction and refund or route it manually; it takes longer than an automatic order, but the money comes back. (XMR to USDT exit)
Conditionally recoverable: sending a token the provider doesn't support, or depositing to a smart-contract address that doesn't handle direct transfers. Recovery ranges from easy to impossible depending on the destination contract — this one needs support, and sometimes the answer is genuinely no.
Usually not recoverable: sending XMR to a BTC address, or an EVM-chain token to a Bitcoin address. The recipient address is on a fundamentally different ledger — no one controls it on the destination chain, and there's no one to ask. Cross-shape mistakes like this are the ones that stick.
Prevention takes 10 seconds: once the order page shows the deposit address, check the network field above it matches what your wallet is about to send, and verify the deposit address starts with a character pattern native to that chain (XMR addresses start with 4 or 8, Solana addresses are base58, TRC20 addresses start with T...). Send a small test amount first for anything over a few hundred dollars. (SOL to XMR guide)
One VeilSwap-specific note: the order page shows a four-step progress bar with both the payin and payout transaction hashes as they land. If your deposit shows as detected but on the wrong network, the order goes to review — and the refund, when it's possible, goes back to the original sending address automatically.