If your transfer is pending, shared route liquidity may have been used by other transfers before yours reached payout. First check whether your source transaction confirmed, then avoid sending the same amount again until its status is clear. On a pool-based route, concurrent demand can delay payout or change the available quote, but it does not by itself prove your funds are lost.
- Check the source transaction before retrying.
- Understand how other transfers can use the same liquidity.
- Retry only after you know which stage failed.
Check the source before resending
A pending transfer can mean the source transaction is still waiting for confirmation, or that it confirmed while the destination payout is waiting. Those are different stages, so look up the source transaction ID in that chain’s public explorer first.
For a transfer sent on Solana, Solana Explorer shows whether the transaction landed and its status. If the source transaction failed, the bridge may never have received the funds, though the failed attempt can still use network fees. If it confirmed, save the transaction ID and check the bridge’s status record before trying again.
Mayan Bridge is a cross-chain bridge and swap service, a category that can move assets between chains and swap them as part of the same transfer. The general checks here help you tell whether the wait is on the source chain or the payout side.
Shared pools can be depleted by concurrent transfers
On a pool-based route, liquidity is the inventory available to pay transfers on the destination chain. A bridge may rely on that inventory to deliver funds quickly, then replenish it later from the source side. Other transfers using the same route can draw from the same pool while yours is in progress.
Say a route has 1,000 USDC available. If transfers for 300 and 500 USDC are paid first, only 200 USDC remains for an incoming 250 USDC request. That last request may wait for the pool to refill, be split or rerouted if the system allows it, or fail at payout. This is an illustration, not a promise that every bridge processes transfers in that order.
The deciding factor is usable liquidity on the exact route and asset, not the total value locked across a whole bridge. A pool can have plenty of funds on another chain or in another token and still lack the asset needed for your destination payout.
Retry only after you know which stage failed
If the source transaction is still unconfirmed, wait for its chain to settle before starting another transfer. If it confirmed and the payout is pending, repeated sends can create duplicate transfers and spend more source-chain fees. Check the transaction IDs and route status first; a new quote may also differ because other transfers changed available liquidity or market prices.
If the destination transaction failed, follow the route’s stated recovery process and keep both transaction IDs. A failed payout does not have one universal remedy: depending on the bridge design, funds may be retried, returned, or require another action. Do not assume a refund is automatic.
When you are ready to make a fresh cross-chain move, Mayan Bridge can move and swap crypto assets across supported chains in one flow. I would compare the fresh quote with the amount you need, then submit only after the earlier transfer’s status is clear; that avoids treating a shared-liquidity delay as a reason to pay twice.
- Verify whether the source transaction confirmed.
- Allow for other transfers to use the same route liquidity.
- Check the failed stage before retrying.