A cross-chain swap changes both an asset position and the network on which the received asset is held. For example, a user might exchange native bitcoin for ether delivered on Ethereum. This differs from a same-chain token swap and from merely moving a representation of the same asset between networks.
Several routes can produce the result
A service may combine a bridge with exchange transactions, use liquidity held across multiple chains, or arrange an atomic swap between counterparties. These approaches have different custody, verification, and settlement assumptions. The phrase cross-chain swap does not identify a single technical standard.
The destination asset may be native or wrapped, depending on the route. Its contract address and network matter as much as its displayed ticker. A familiar token name does not establish identical backing or redemption rights.
Settlement spans separate systems
Source-chain confirmation does not by itself prove that the destination payment has completed. Each network has its own transaction processing and finality, while routing services can add delays or restrictions.
The quoted output must be considered alongside fees, slippage limits, destination liquidity, and failure or refund rules. Contract bugs, compromised verification, and chain reorganizations can affect delivery. An easy one-screen interface does not remove the dependencies underneath it.