Before a Cross-Chain Swap Pays Out, Several Checks Come First

Before a cross-chain swap pays out, the source deposit must be recognized, the trade route must execute, and a transaction must deliver the output on the destination chain. That sequence is longer than a same-chain swap, where one chain can settle the trade in a single transaction. The steps between deposit and payout depend on the route: some systems swap through protocol vaults, while others use a bridge or a relayer that advances funds.

What happens after you send the deposit?

After you send funds, the service or protocol waits until it can treat the source-chain transaction as valid. A transaction appearing in a wallet or block explorer does not necessarily mean the route can safely proceed; protocols set their own rules for recognizing deposits and handling chain reorganizations. The wait can vary with the source chain and the system’s confirmation policy.

Next, the route identifies how to turn the input into the asset you requested. That may involve one swap or several steps across liquidity pools and chains. In THORChain’s vault model, its documentation describes external-chain transactions being observed and processed before assets move through protocol liquidity and an outbound transaction is issued. A fuller explanation of the mechanics is available in this thor swap overview. The useful comparison is that a cross-chain route has to coordinate activity across separate ledgers; there is no single shared transaction that updates both at once.

Other designs change who supplies the destination funds and when. Across’s documentation, for example, describes a relayer paying the user on the destination chain, then seeking reimbursement after the deposit and fill are verified. This can make the user-facing payout arrive before the protocol has finished its own settlement. In a vault-based flow, by comparison, the payout generally follows the protocol’s observation and swap process. “Swap complete” can therefore mean that you have received funds, even while backend accounting is still underway.

Why can the amount or timing differ from the quote?

A quote estimates the result under conditions that can change before execution. The available pool liquidity, the size of the trade relative to that liquidity, and any intermediate swaps can affect the final amount. THORChain’s documentation describes liquidity fees that vary with pool impact; its streaming swaps split some trades into smaller executions over time, trading a longer wait for the possibility of lower price impact. Other routes may use different execution rules, so a quote is only as useful as its assumptions and expiry.

Fees also come from different places. The sender pays the source chain’s transaction fee to submit the deposit. The route may deduct a trading or service fee from the amount being swapped, and the destination transaction needs gas too. THORChain documents an outbound fee for destination-chain costs; across protocols, the exact fee breakdown depends on the route. A displayed estimate should be checked for whether it includes both the swap costs and the final payout fee.

Timing has the same split. Source-chain confirmation, route execution and destination-chain confirmation are distinct events, and congestion can affect any of them. A relayer may deliver the output quickly by fronting funds while waiting for reimbursement; a route that waits for more of its cross-chain process to finish may take longer before the user sees a payout. Faster visible settlement shifts some delay and risk into the system’s later verification and accounting.

What should you check while waiting for payout?

Track the swap by its source transaction and the destination transaction, if one has been created. A pending status may mean the deposit is still awaiting confirmation, the route is executing, or the payout has been submitted but not yet confirmed on the destination chain. These stages call for different expectations; a source transaction that has not been recognized is not the same as a payout transaction waiting for destination-chain inclusion.

• Confirm that the source transaction succeeded and went to the deposit address or contract specified for the swap.
• Check that the receiving address and destination network match what you intended; an address for one network may not work on another.
• Compare the quoted minimum output and fee breakdown with the route’s final status, especially if the swap took time to execute.
• Use the service’s stated refund or recovery process if the route reports a failure; do not assume a stalled status means funds have already returned.

For most readers, the practical distinction is whether the route pays only after its own cross-chain execution or lets a relayer advance the destination asset before reimbursement. The former makes the order of operations more visible; the latter can shorten the wait to payout while leaving settlement to finish later. Watch the source confirmation, route status, minimum-output conditions and destination transaction next. Those signals show where the swap is in the process—and whether a delay is still part of execution or has become a recovery issue.