Pre-send checks every swapper should run

Sending cryptocurrency to an exchange address feels like a one-way door. You click, the transaction confirms, and then you wait. What happens inside that wait is a sequence of events that most people never see. Understanding it is the difference between a swap that lands in minutes and one that vanishes into a support ticket.

What actually happens when you send funds

Your coins leave your wallet and arrive at the exchanger's address. That is the only part you control. From there, the exchanger must detect the incoming transaction, match it to your swap request, check that the amount and network are correct, and then send your output coins to the address you provided. Every step depends on the block confirmation count required by the exchanger. Bitcoin needs more confirmations than Solana. Some networks need a minimum number of blocks before the exchanger will touch the funds.

During this process, your swap exists as a record in the exchanger's system. That record is your What an exchange reference is and why you should keep it. The reference ties your deposit to your expected output. Without it, the exchanger has only a raw transaction hash and a destination address - and those can look identical to a thousand other swaps that day.

The checks that should happen before you send

How to verify a swap deposit address before sending funds starts with the URL in your browser. Every exchange site has a domain. A clone site uses a domain that looks similar but is not the same. Check the address bar. Bookmark the real site. Do not click through from a search result or a social media link. How to tell a real exchange site from a clone is straightforward: a clone cannot access the real exchanger's wallet. If you send to a clone, your funds go to a scammer's wallet and no mechanism exists to recover them.

The address itself must match the one generated for your specific swap. Do not reuse an address from a previous swap. Why a second deposit to the same swap address is dangerous is that the exchanger's system treats each swap as a separate order. A second deposit to an old address may land in the system without any open order to attach to. The funds become unallocated. Recovery is possible, but it requires manual intervention and a support ticket. Avoid the problem entirely: generate a fresh address for every swap.

Check the network. If the exchange address is for an Ethereum token and you send on the BNB Smart Chain, the transaction confirms successfully - but the exchanger never sees it. The coins exist on the wrong chain. Which mistakes in a swap are recoverable and which are not depends on the network. Sending to the correct address on the wrong chain is often recoverable if the exchanger supports that chain and can access the wallet. Sending to a completely wrong address, one you typed manually or pasted incorrectly, is almost never recoverable. No one controls that private key but whoever generated it.

After you send: the waiting period

The transaction appears in the mempool, then in a block. The exchanger waits for a certain number of confirmations. That number varies by asset and by the exchanger's risk model. How long to wait before treating a swap as failed is usually two to three times the expected confirmation time for that network. For Bitcoin, that might be two hours. For Solana, it might be ten minutes. If the swap status page shows no movement after that window, the swap may be stuck.

crypto-swap-is-stuck-as-pending/">What to do if a crypto swap is stuck as pending starts with checking the block explorer. If the transaction shows enough confirmations but the swap still shows pending, the exchanger may be processing a backlog. Wait another fifteen minutes. If nothing changes, locate your exchange reference and open a support ticket. Without the reference, the support team has to search by transaction hash, which is slower and less reliable.

When a swap fails

Swaps fail for many reasons. The output token's liquidity may be insufficient. The price may move beyond the slippage tolerance. The network may be congested and the transaction never confirms. In each case, the exchanger should return your original funds minus any network fees.

How an exchanger returns funds when a swap fails depends on whether the deposit was already confirmed. If the exchanger detected the deposit but could not complete the swap, it sends your original coins back to the address they came from. That return transaction has its own fee and its own confirmation time. If the exchanger never detected the deposit - because you sent to a wrong address or the wrong network - there is nothing to return. The funds are gone.

Recoverable mistakes: sending the correct amount to the right address on the right network but the swap times out. You get your coins back. Unrecoverable mistakes: sending to a clone site, sending to a wrong address, sending on a network the exchanger does not support at all. Those coins are not coming back.

The one check that covers everything

Before you click send, verify three things: the domain, the address, and the network. Then copy the exchange reference from the swap page. That string of characters is your only proof that a specific swap exists. Keep it until the output coins arrive in your wallet. If something goes wrong, that reference is what the support team needs to find your order.

Most swaps work exactly as expected. The ones that do not are almost always the result of a check skipped in the last ten seconds before sending. Slow down. Look at the address. Look at the network. Look at the domain. Then send.