Why Your Across Bridge Transfer Is Still Pending

A pending Across transfer usually means your deposit is waiting for funds to be sent on the destination chain. Across holds the source tokens while a relayer, a service that fronts funds, or the protocol’s fallback process completes the transfer. Check the transfer status before sending again, so you do not mistake a delay for a failed deposit.

How does an Across transfer move between chains?

Across says a transfer starts when your tokens are deposited into a pool on the source chain. A relayer can then send the requested tokens to your address on the destination chain using its own funds. The relayer is repaid later through Across’s settlement process, which runs in the background after your destination funds arrive.

If you are unsure which transfer route or type you used, this guide to Across bridge transfer types explains the differences. The key point here is that “pending” usually refers to the fill: the destination payment has not yet been recorded. Settlement is a separate step and does not usually require you to wait before using funds already delivered.

Why can an Across transfer stay pending?

Across’s documentation says relayers may not fill a deposit quickly if the requested amount is unusually large, the token pair is unusual, relayer service is temporarily unavailable, or the fee does not make the request attractive enough. The source chain may also need time to reach a level of confirmation relayers accept before they front funds.

When relayers do not fill a deposit, Across can use liquidity-provider funds for a “slow fill,” its fallback payment path. Across says this takes longer because the fill is processed through a protocol bundle and challenge period. The transfer status should show whether it is still waiting, filled, expired, or refunded.

What should you check when a transfer is pending?

Use Across’s status tracker with the source transaction hash or deposit ID, then compare the result with the source chain explorer. Across says the tracker updates about every 10 seconds. Check these details before taking another action:

• Confirm the source transaction succeeded and deposited the intended token and amount.
• Check that the destination chain and recipient address match your request.
• Read the status tracker for a fill, expiry, or refund update.
• If the deposit has expired, allow time for the refund process to finish.

Across says an expired deposit can take several hours to refund because it must pass through settlement and cross-chain steps. A pending status alone does not show that the deposit failed. If the tracker does not recognize a successful source transaction, or the status remains unclear, use Across’s official support route with the transaction hash. Do not submit the same transfer again until you know what happened to the first deposit.