Why an approved token still cannot complete a swap
A SyncSwap swap can fail after approval because allowance, balance, gas or quote conditions still block the separate transaction. Read the receipt and retry safely.
SyncSwap swaps can fail after token approval because approval grants spending permission, while the swap is a separate transaction that still needs the right allowance, funds and valid trade conditions.
- Unsent or pending: A wallet request may not have been confirmed, or the swap may still be waiting.
- Reverted: A submitted swap can fail because of allowance, balance, gas, quote changes or token restrictions.
- Retry: Read the transaction receipt, fix the matching cause, then review fresh terms before confirming again.
SyncSwap is a decentralized exchange for trading tokens and accessing liquidity pools on supported networks. The SyncSwap topic adds background on the service involved; the checks below help identify why a particular swap did not complete.
First identify whether the swap was sent or reverted
A wallet rejection means the swap request was not submitted, while a pending transaction has not yet finished. A reverted transaction has a receipt with a failed status. Find the transaction hash if one exists, then read its receipt and any error shown by the wallet or transaction viewer before retrying.
The approval can succeed even when the later swap reverts. ERC-20 allowance records which account owns the tokens and which spender may use them. If the approval transaction succeeded, that permission can remain in place after a separate swap fails. You may be able to reuse it, but first confirm the allowance covers the intended trade and names the correct spender.
Match the fix to the failure
- Wrong account, chain or token: An allowance or balance on a different account, network or token will not cover this trade. Select the matching wallet account, chain and asset, then check the available balance and allowance.
- Too little allowance or token balance: The swap may need more permission or more tokens than the account holds. Approve the needed amount if required, and make sure the input balance covers the trade.
- Not enough native funds for gas: Approval uses gas, and the swap needs its own gas payment. Keep native funds available for the second transaction; a successful approval does not pay for the swap.
- Changed output or expired quote: A router can enforce a minimum output and a deadline. If the price moves or the quote expires before execution, the swap can revert. Refresh the quote, review the minimum received, and confirm only if the terms still suit you.
- Restricted token transfer: Some tokens restrict when or how they can move. If the receipt points to a transfer restriction, stop retrying that route unless you can confirm it supports the token.
When none of these signs fits, do not keep resubmitting the same trade. Preserve the receipt error, recheck the selected account and token, and investigate the specific failure before trying again. Avoid blindly increasing slippage: it changes the minimum output you accept and may not fix an allowance, gas or token restriction.
Related questions
Do failed swaps cost gas?
A reverted transaction included on-chain consumes gas, even though the swap failed. A wallet request rejected before execution incurs no transaction fee.
How do I revoke token approval?
Use a trusted allowance tool to set the permission to zero, then confirm the revocation transaction. That separate transaction also needs gas.
Before retrying, refresh the quote and read the minimum received before confirming. This catches stale terms without needlessly raising slippage.