Why a Crypto Bridge Transfer Stays Pending

A pending bridge transfer means your request has started, but the destination chain has not yet recorded the funds. The delay may be part of the bridge’s normal process, or a step may need checking. A bridge moves assets or messages between blockchains, which cannot directly share transaction records.

Most transfers pass through several steps: the source chain accepts the transaction, the bridge confirms it, and the destination chain processes a matching instruction. For a closer look at how route choices affect a move, read this Manta Bridge guide to transfer routes. The exact steps and status labels vary by bridge.

What does “pending” mean in a bridge transfer?

“Pending” means the transfer has not reached its final state, but the label alone does not tell you which step is waiting. Check the source transaction first: if it is still pending on its own chain, the bridge may not have received a confirmed request. If it is confirmed, the bridge may still be preparing or delivering the instruction for the destination chain.

Some bridges use a relayer, a service that carries a transaction message between chains. Others rely on a proof—evidence that the source-chain event happened—or use liquidity already available on the destination chain. These designs affect what happens while a transfer is in progress. A bridge that sends a separate destination transaction may show a second transaction hash once that step begins.

How does a pending transfer resolve?

A pending transfer resolves when the required steps finish and the destination chain records the result. In many cases, that happens without any action from you. The source transaction reaches finality—the point at which it is treated as settled—then the bridge completes its checks and submits or releases the destination-side funds.

Check the bridge’s status page or transaction view for the source and destination steps. The source-chain explorer can confirm whether the original transaction succeeded; a destination-chain explorer can show whether the funds arrived. If a bridge offers a claim step, its instructions should say when that is needed. A transfer that fails may instead be eligible for a refund or recovery, but the rules depend on the bridge and its design.

• Source transaction pending: Wait for the source chain to process it.
• Source transaction failed: Check whether the assets stayed in your wallet and whether the bridge lists a recovery path.
• Source confirmed, destination pending: Follow the bridge’s status and any stated claim or retry instructions.
• Destination transaction complete: Check the destination wallet, network and token balance.

What should you do if it stays pending?

Use the transaction hash and the bridge’s official status view to identify the last completed step. Check that you are viewing the destination wallet on the intended network; a token may not appear in a wallet’s default asset list even when it has arrived. Give the bridge time if its status still shows a step in progress, since chains and bridge processes do not all settle at the same pace.

If the status has stopped changing, use the bridge’s official support route and provide the transaction hash and relevant networks. Do not submit the same transfer again unless the bridge clearly says it is safe; a second request can create a separate transfer. Never share a recovery phrase or private key to “unstick” a transfer. The useful distinction is whether the source transaction failed, the bridge is still processing it, or the destination transaction completed but the wallet has not displayed the asset.