A Pending Bridge Transfer Usually Needs a Check, Not a Retry
A pending bridge transfer can be waiting on confirmation, delivery or a wallet update. Check its source transaction before retrying to avoid sending a second deposit.
The Aeterna Sol Editors

One pending bridge transfer usually calls for a check before a retry. Its status means a step has not finished or the app has not yet caught up.
A bridge moves value between separate blockchains, so a transfer can involve more than one transaction. First, the source chain records your deposit or burn; then the bridge processes that message or matches it with destination liquidity.
Why is my bridge transfer still pending?
A transfer can wait at several points. Your wallet may still be submitting the source transaction, the source chain may need more confirmations, or the bridge may be processing the deposit before funds appear on the destination chain.
These stages are different. A wallet that says “pending” may mean the source transaction has not been included in a block. A bridge app can show “processing” after the source transaction is confirmed but before the destination transaction is complete.
Some bridges use a relayer or validators to pass information between chains. Others use liquidity providers to send funds on the destination chain while the source side settles. Each design has its own processing steps, so the app’s status is only a useful starting point.
If you need the basic wallet steps, read how to move crypto with acrossbridge. For a transfer already in progress, the source transaction is the better place to begin your checks.
How can I tell which step is waiting?
Find the source transaction hash in your wallet or bridge history, then open it in the explorer for that blockchain. The explorer shows whether the transaction is pending, confirmed, failed or missing from the chain.
If it is confirmed, check the bridge’s own status page or transaction record. Look for a destination transaction hash, a claim step, or instructions for a transfer that needs recovery. Use the bridge’s official site and confirm that its network and token match your transfer.
Work through these checks in order:
- Confirm the source network, destination network, token and amount in the transfer details.
- Check the source transaction hash on the correct chain’s explorer.
- If the source transaction is confirmed, check the bridge’s status and destination transaction.
- Refresh the wallet or reconnect it to the destination network, then check the token balance there.
A confirmed source transaction is useful evidence that your request reached the chain, but it does not prove that delivery is complete. A destination transaction or an official claim step is stronger evidence that the next stage has finished.
Also check whether you are viewing the destination network in your wallet. A token may not appear in the balance list until you add its contract, and some wallets do not show every supported asset automatically.
When should I retry a pending bridge transfer?
Retry only after you know which stage failed and what the bridge means by “retry.” A button that resumes processing or claims an already completed transfer may be appropriate; starting a new deposit can send your funds through the bridge again.
If the source transaction is still pending, do not create another deposit just because the bridge page has not changed. Check your wallet’s transaction details and follow its instructions for that transaction. Replacing or cancelling a pending wallet transaction can affect what gets submitted, so verify the network and amount before signing anything.
If the source transaction failed, the bridge may not have received the deposit. Confirm the failure in the chain explorer and check whether the funds remain in your wallet before starting over. If the source transaction succeeded but destination delivery is delayed, use the bridge’s official recovery or claim process if it offers one.
Before taking action, make sure the recovery page is the bridge’s genuine site. Never share your seed phrase or private key, and read each wallet prompt before signing; a message that asks for broad token approval can authorize a contract to move tokens beyond this transfer.
Wait when the source transaction is confirmed and the bridge still reports processing, unless its official status or support instructions say to take a specific recovery step. Retry only when the original attempt is confirmed failed or the bridge explicitly tells you to resume it. That approach helps you avoid duplicate deposits while giving the transfer’s actual stage time to resolve.