What a Cross-Chain Swap Approval Actually Authorizes

Approving a cross-chain swap lets a specified spender use a specified amount of your source-chain tokens; it does not itself move tokens or start the swap. The swap starts only when you submit and confirm the separate transaction that calls the route’s contract.

That distinction matters because a cross-chain swap is a sequence of actions, not one simultaneous operation across two blockchains. First, an approval may establish permission on the source chain. Then a swap transaction spends tokens into a route, which may exchange them before or after a bridge transfer. For a closer look at the route and settlement, see how quickswap settles cross-chain swaps.

What does the approval transaction authorize?

On an EVM chain, an ERC-20 approval sets an allowance: the amount of a token that a designated spender can transfer from your address. The spender is usually a router or another contract in the route. Some flows use a separate permission contract, such as an allowance manager. The wallet prompt should identify the token, spender and allowance amount.

The approval changes permission recorded by the token contract. It does not transfer the approved tokens, reserve a quote, or guarantee that a later swap will succeed. The approval transaction is sent to the source chain and must confirm there before the spender can use that allowance. It also consumes source-chain gas.

A route may request permission for the exact input amount or for a larger amount. A larger allowance can avoid repeating the approval for later swaps, but it also leaves the spender with permission to transfer more tokens than this trade needs. Check the spender address and amount against the transaction details. If the prompt does not match the route you chose, do not sign it.

Some flows use a token authorization signature instead of a separate on-chain approval transaction. That changes how permission is submitted, but the permission still concerns a token and a spender. Native assets such as ETH do not use ERC-20 allowances; a route handles them through the transaction’s native-value field or a wrapping step.

What happens after you approve?

After the allowance is in place, the swap transaction submits the route’s instructions on the source chain. The contract can then transfer the approved input from your wallet and execute its source-side actions. Depending on the route, these may include a token swap, a deposit into a bridge, or both.

The route’s order matters. It may swap the input into a bridgeable token before sending it across chains, or bridge the input first and swap it on the destination chain. Some routes use a bridge token as an intermediate asset. The quote describes the intended route and output, but the approval does not bind the route to a guaranteed destination result.

Once the source transaction succeeds, the bridge mechanism must complete its own settlement. Depending on its design, it may lock or burn assets on the source chain and release or mint assets on the destination, or use liquidity providers to deliver assets there. A destination-side swap may then convert the delivered token into the requested output. These steps are coordinated by the route, but they are not one atomic transaction across both chains.

Does approval mean the swap has settled?

No. Approval confirms permission; a successful source-chain swap transaction confirms that the route began executing; destination settlement confirms that the requested output was delivered. These are different events, and an interface may show them as separate statuses.

If the approval confirms but the swap transaction is rejected, reverted or never submitted, the cross-chain transfer has not started. If the source transaction succeeds, the bridge may still be processing. A destination-side action can also fail after source execution. The route’s recovery behavior depends on its contracts and bridge design, so a source-chain transaction hash alone does not establish that the destination token arrived.

For a pending swap, track the route using its status page or transaction identifiers, and verify the destination wallet balance before treating the trade as complete. Do not submit another swap just because the destination balance has not updated yet: the first route may still be settling.

• Confirm the source chain, input token and amount in the wallet prompt.
• Check which contract receives the allowance and whether the amount is limited to this trade.
• Review the separate swap transaction before signing; approval alone does not execute it.
• Wait for destination delivery or a clear failure status before retrying.

The practical rule is simple: an approval grants spending authority on one chain, while the swap transaction uses that authority to enter a route. Bridge settlement and any destination-side swap happen afterward, and each has its own confirmation and failure states.