5 acrossbridge Steps When Token Approval Is Missing

An acrossbridge transfer with missing token approval takes five steps: check the allowance, approve the spender, refresh the quote, deposit, and verify delivery. For a treasury sending an ERC-20 token, acrossbridge clears the missing-approval hold-up after the origin wallet authorizes that spender; Across Bridge relayers can then deliver funds on the destination chain.

Key points

• Approval gives a contract permission to spend a token; it does not send the transfer.
• Approve the spender and amount shown for the current route, then wait for confirmation.
• Get a fresh quote before depositing, especially when a multisig approval takes time.

Why does acrossbridge need token approval?

An ERC-20 transfer needs an allowance because the origin-chain contract must pull tokens from your wallet when you deposit. The allowance belongs to a specific token, spender, wallet, and chain. An approval left over from another token or contract will not satisfy the current transfer, even if the wallet holds enough funds.

For example, a treasury may have 1,000 USDC on Arbitrum but see an insufficient allowance for a payment to Optimism. Signing the approval fixes that permission only. The separate deposit transaction creates the transfer intent: it escrows the input tokens, and a relayer uses its own funds to pay the recipient on the destination chain. The relayer is repaid later through the protocol’s verified settlement process.

Five steps to prepare and send the transfer

1. Get a quote for the exact transfer. Enter the origin and destination chains, token contracts, amount, and recipient address. For a 1,000 USDC treasury payment, check that the quoted route supports that amount and that the wallet has USDC plus the origin chain’s gas token. Compare the quoted allowance with the required amount; a token balance alone does not establish permission.
2. Approve the quoted spender on the origin chain. Check the token contract, spender address, chain, and allowance in the wallet or multisig transaction before signing. A common mistake is to treat the approval confirmation as proof that the payment was sent; no deposit has happened yet. An allowance limited to the planned amount reduces continuing exposure, while a larger allowance can avoid repeated approval transactions for regular payouts.
3. Wait for approval confirmation and refresh the quote. A multisig proposal must be executed on-chain, not merely signed by enough team members. Confirm that the new allowance covers the quoted input, then check the recipient, output amount, fees, and quote expiry again. If approval took long enough for the quote to expire, use the new transaction details rather than submitting the old deposit.
4. Submit the deposit transaction. Check that the transaction is simulated successfully and that the wallet has enough native token for its gas. The deposit moves the approved tokens into the origin contract and records the recipient and minimum destination output. A relayer can then fill the intent on the destination chain, often within seconds after the origin deposit is observed; network conditions and available relayer liquidity can extend that time.
5. Verify the destination fill and reconcile the payment. Match the origin deposit and destination transaction to the intended recipient, token, and amount before marking a payout complete. Record both transaction hashes, the received amount, and the fees for treasury records. If delivery is delayed, inspect the deposit status before retrying: a second deposit creates a second transfer rather than accelerating the first.

What fees do relayers charge on Across Bridge?

Relayers have no single fixed charge across routes. The quote accounts for destination gas, the relayer’s cost of advancing capital, and its risk while awaiting repayment; a separate liquidity provider fee can rise as a route’s pool becomes more heavily used. The origin wallet also pays gas for the approval, when needed, and for the deposit. Those gas costs matter most on small transfers.

Compare the input and expected output alongside the origin gas before approving. For example, if an illustrative quote takes 1,000 USDC and delivers 998 USDC, the 2 USDC difference is 0.2% of the input, with origin gas still to pay. Request a fresh quote for each batch: gas prices, pool utilization, route, and amount can change the result.

How does it compare with a chain’s canonical bridge?

A canonical bridge uses the chain’s own parent-to-child or child-to-parent transfer path; a relayer-based transfer pays for capital to reach the destination sooner. On Arbitrum One, a canonical withdrawal to Ethereum takes at least seven days before funds can be claimed. Moving from Arbitrum to Optimism through canonical bridges also requires going through Ethereum, adding transactions and time.

The choice depends on the deadline, quoted net output, supported token route, and security process your team accepts. A fast fill arrives before the relayer’s later settlement, which relies on contract rules and a challenge process for invalid settlement proposals. Before authorizing the allowance, ask: does this exact route deliver the required token and amount to the approved recipient within the payment deadline, at a total cost the treasury accepts?