When Is a Cross-Chain Swap Safe to Mark Complete?

Mark a cross-chain swap complete only after the destination-chain transaction succeeds and the expected tokens reach the right address. A confirmed send on the source chain means the swap has started, not that it has settled. Check the destination network, token and received amount before treating the funds as available.

This check separates a transfer that has begun from one you can actually use.

Does a confirmed source transaction mean the swap is complete?

No: source-chain confirmation shows that the first transaction was included, while the cross-chain service may still need to verify it, relay the message and execute a transaction on the destination chain. Those stages can take different amounts of time depending on the chains, route and service. A progress page may label the transfer “pending” or “in transit” while this work continues.

For a useful comparison of how route costs and speed affect the choice, see this fuller guide to choosing a biswap cross-chain swap by cost and speed. The same trade-off matters after sending: a faster route may use different verification or settlement steps, so its displayed estimate is not proof of delivery.

What should you check on the destination chain?

Find the destination transaction using the route tracker or the transaction or message identifier from the source receipt. Open that transaction in an explorer for the destination network and confirm its status is successful. A service dashboard is helpful for tracking, but the destination transaction is the evidence that execution happened onchain.

Then check that the assets match what you intended to receive. Confirm the receiving address, token contract and network; token names and symbols can be copied, so the contract address is a stronger identifier. Compare the actual amount with the quote, allowing for the fees and price impact disclosed when you submitted the swap.

• Source transaction is included and has reached the route’s required confirmation level.
• Destination transaction is successful, not merely submitted or awaiting execution.
• Expected token contract and network appear at your intended address.
• Received amount is consistent with the route quote after stated fees and slippage.

A successful destination transaction can still deliver less than the quoted amount if the route’s terms allow slippage. The token may also need to be added to a wallet’s display before it appears in the balance list; check the address and token contract before concluding that delivery failed.

What if the swap is delayed or the amount is different?

If the source transaction succeeded but there is no successful destination transaction yet, treat the swap as pending. Check the route’s stated processing steps and look for an update or destination transaction hash before taking another action. Sending a second swap can create a separate transfer rather than speed up the first one.

If destination execution failed, use the route’s status details to see whether it supports a retry, refund or recovery process. These options depend on the protocol and the failure stage, and may involve a further transaction fee. Keep the source receipt and message identifier available if you need to follow up.

The practical rule is simple: mark the swap complete when destination execution succeeds and the intended asset is verifiably at the right address. Until then, a source confirmation is progress, not settlement.