What should I do if I sent a swap deposit from my phone but the transaction is stuck

21 September 2026

Check the transaction status on a blockchain explorer, then contact the exchanger's support with the transaction hash. Do not send a second deposit or try to cancel the transaction on your own, because you can lose both funds.

A stuck transaction usually means the network is congested, or you set a gas fee too low for the current conditions. On a phone, wallets often apply a default fee that works in normal times but becomes insufficient during traffic spikes. The transaction is broadcast to the network and waiting to be confirmed, not lost.

Your first step: copy the transaction hash (TXID) from your wallet's history. Paste it into a block explorer for the relevant network - Ethereum uses Etherscan, Binance Smart Chain uses BscScan, and so on. The explorer shows the current status: "Pending", "Success", or "Failed (out of gas)". If it says pending, the network simply has not included it yet.

If the transaction is pending for more than an hour, you have three safe options:

1. Wait longer. Some networks clear backlogs within hours. If your fee was only slightly low, miners may eventually pick it up.

2. Use your wallet's "speed up" or "replace" feature. Many mobile wallets let you send a new transaction with a higher gas fee that replaces the stuck one. This only works if your wallet supports nonce management and the original transaction has not been confirmed. Do this only if you understand the wallet's interface - pressing buttons blindly can send a second deposit.

3. Contact the exchanger's support. Provide the TXID, the token type, the amount, and the wallet address you used. The exchanger can see the pending transaction on their end. They will tell you whether to wait, replace, or consider the swap failed. Never send funds again unless support explicitly instructs you.

The most common phone-specific mistake: closing the wallet app or switching away before the transaction confirms. This does not cancel the transaction - it still sits on the network. But you lose the ability to monitor it easily, and you may not notice when it finally confirms hours later, leading you to think it failed.

Another phone pitfall: the wallet shows the transaction as "sent" but the explorer shows nothing. That means the wallet never broadcast it properly - often because a poor mobile connection dropped the submission. In that case, resend from the wallet. The original broadcast attempt left no trace.

If the transaction eventually confirms but the swap site does not credit your deposit, contact support with the successful TXID. Delays happen when the site's monitoring script misses the confirmation during a brief downtime. Most exchanges resolve this within a few hours.

The hardest case: the transaction confirms, but to the wrong address or wrong network. For example, you sent BEP-20 tokens to an ERC-20 address. That is not a stuck transaction - it is a misrouted one. Recovery depends on whether anyone controls the destination address. Support cannot reverse a confirmed on-chain transfer. This is why verifying network and address before sending is critical.

If you are dealing with carbon credit tokens, the same rules apply, but the token contracts may have unusual decimals or transfer restrictions that cause confirmations to stall. The exchanger's support team handles these tokens regularly and can advise faster than general wallet support.

For a complete walkthrough of what goes wrong specifically with mobile wallets and carbon credit tokens, read the hub page: "Mobile wallet swap mistakes with carbon credit tokens". It covers the full set of phone-specific errors that lead to stuck or lost deposits.

Back to carbon credits