A cross-chain swap trades asset A on chain X for asset B on chain Y in one flow: the trade and the bridge happen together, signed once, settled to the destination address. Without it, moving value between chains means two transactions, a bridge balance, and an evening of tab-switching.
The hard part of bridges has always been trust: who holds the in-flight value? Modern routing answers with liquidity pools and verified message passing rather than custodial bridges, keeping the non-custodial property end to end.
A cross-chain swap exchanges asset A on one chain for asset B on another, in one signed flow. Where both assets have native forms with liquidity, the trade routes through pools on each side with value crossing between the legs; where a token exists on both chains, the engine moves between its forms. From the signer's seat it is one quote and one approval, with the destination address on the other chain.
What distinguishes it from a plain swap is the settlement surface: two chains must each finalize their leg, so elapsed time follows the slower chain. The fast case is an L2-to-L2 pair settling in seconds; the slow case involves a mainnet leg waiting for fuller confirmations.
The alternative history here is the bridge-with-custody model, and its failure record is why liquidity-based crossing is preferred where forms exist. Value moves through markets rather than through a pooled vault waiting to be exploited.
A holder of an Ethereum mainnet position wanting Solana exposure quotes ETH against a Solana asset, signs once, and receives on Solana once both legs finalize. The reverse works identically, and the quote shows the expected arrival time alongside the amount.
The swap screen routes cross-chain natively: pick what you hold on its chain, pick what you want on its chain, and the router bridges alongside the trade in a single signed transaction.
Cross-border checkout is the merchant-facing version: a buyer on any chain pays into a settlement asset on the chain the merchant prefers. The corridor decides nothing about the invoice; routing absorbs the geography. The accounting note: a cross-chain receipt is one economic event with two chain records, the outbound leg on the buyer's chain and the inbound on yours. Keep both hashes. Reconciliation joins on the invoice reference either way, but auditors like the pair, and the export from the payment record carries both.
Every term behind the rails, the assets, and the settlement.