Why Is an Across Bridge Transfer Pending? A Practical Troubleshooting Guide
An Across Bridge transfer that appears pending is not automatically lost or failed. First confirm that the origin transaction succeeded, then determine whether the deposit is still waiting for a fill, has expired, or was completed on a different network or token than the one displayed in your wallet. Do not submit a second transfer until you have checked the transaction receipt, recipient address, destination chain, token contract, and transfer status.
Confirm that the deposit transaction succeeded
Start on the origin chain, where you sent the funds. A wallet notification saying “submitted” is not enough. Open the transaction record and check whether it is confirmed, reverted, or still waiting for block confirmation.
- Confirmed: continue to the deposit-status check.
- Reverted or failed: the bridge may never have received the deposit. Investigate the failed transaction rather than waiting for a destination transfer.
- Still pending on the origin chain: wait for confirmation before diagnosing the bridge.
Save the transaction hash, the sending address, the recipient address, the origin chain, and the destination chain. These details distinguish a delayed transfer from a transfer sent with incorrect parameters.
Separate a pending fill from a missing wallet balance
If the origin transaction is confirmed but the destination wallet has not changed, check whether the wallet is connected to the destination network. A wallet can hold the funds while displaying a zero balance simply because it is showing the origin chain.
Also verify the destination token. Identical symbols do not prove that two assets use the same contract. Token addresses and decimal formats can differ between chains, so compare the contract shown in the transfer details with the asset imported into the wallet.
If you need to check how the selected route is supposed to work, use this cross-chain route explanation to understand the Across Bridge process before repeating the transaction. It cannot replace the transaction receipt or status record, so keep those records available when checking the result.
Use the status label to choose the next action
Across transfer records commonly distinguish between a deposit that is waiting, one that has completed, one that has expired, and one that has been refunded. Each state calls for a different response.
| Status or symptom | What it usually means | Next action |
|---|---|---|
| Pending | The deposit was submitted but has not yet been filled. | Wait, then check the status again. Avoid sending another amount. |
| Filled | The destination-side transfer was completed. | Switch to the destination chain and verify the recipient address and token contract. |
| Expired | The fill deadline passed without completion. | Wait for the refund process; do not treat expiration as permission to retry immediately. |
| Refunded | The funds were returned to the configured refund address. | Check that address on the origin chain before starting a new transfer. |
Most mainnet fills are described as taking roughly a few seconds, but that is an expected performance figure rather than a promise for every route. Large transfers, unusual token pairs, network congestion, or reduced relayer activity can create longer waits.
Check route, token, and amount restrictions
A route can fail to produce a usable quote even when both chains are individually familiar. Support is determined by the specific combination of origin chain, destination chain, input token, output token, and amount.
- Confirm that the origin and destination chains are the intended networks.
- Confirm that the token is supported on both sides of the route.
- Check the quoted minimum and maximum amount before signing.
- Compare the recipient address with the address controlled by the wallet.
- Review the expected output and fees immediately before approval.
Do not rely on a token symbol alone. USDC, ETH, and other common symbols can represent different contracts, and a bridged version may not be interchangeable with a native version in a destination application.
Expired transfers need patience, not another deposit
An expired transfer is different from a failed origin transaction. When a deposit reaches its deadline without a fill, the funds may remain in the origin-side contract while the refund is processed. That refund is not necessarily immediate; settlement and chain confirmation can take hours.
During that period, monitor the original transfer and identify the configured refund address. Starting a second transfer before the first one is resolved can create two separate exposures and make the accounting harder to follow.
The safest decision rule is simple: if the origin transaction failed, diagnose the transaction; if the deposit is pending, wait and monitor; if it is filled, inspect the destination network and token; if it is expired, wait for the refund. Only after the first transfer reaches a clear terminal state should you prepare a replacement transaction.