I approved a token but received nothing: did I swap?
Identify whether your confirmed transaction granted a token allowance or actually exchanged tokens, then resume the correct step.
The reference
Browse 484 guides to DEX aggregation, BNB Chain, swap execution and integration.
Identify whether your confirmed transaction granted a token allowance or actually exchanged tokens, then resume the correct step.
Determine whether repeated swap clicks created duplicate requests, same-nonce replacements or two independently executable trades.
Distinguish a consumed permit nonce from the wallet account’s transaction nonce when a signed authorization stops working.
Use the transaction hash, block inclusion and receipt to distinguish a waiting swap from a reverted or unsubmitted request.
Collect useful evidence when an explorer reports execution reverted without decoding a clear reason.
Identify whether a missing route reflects token identity, unsupported execution or insufficient liquidity for your exact request.
Check confirmed and replaced transactions before treating a nonce-too-low message as a reason to submit another swap.
Renew the correct authorization when a permit expires, while checking whether the route and token allowance are still valid.
Use a price-impact warning to inspect trade size and available execution, without confusing it with slippage tolerance.
Refresh stale swap instructions and reassess the economic terms when a quote expires before execution.
Evaluate the exact router and token behavior when balances change through rebasing, without assuming every rebase swap must fail.
Why a node can reject a higher-fee replacement and what to check before changing transaction fees again.
Separate a broken wallet connection from the state of a swap that may already have been submitted.
Accelerate an existing pending transaction by replacing its fee bid while preserving awareness of its quote and deadline.
Distinguish raw token units from display decimals when a swap amount appears too large or too small.
Match the application’s connected account with the actual signer and recipient before approving or swapping.
Find out why a reverted swap still costs gas, how to verify the receipt, what happens to your input tokens and what to check before retrying.
Distinguish an exhausted execution gas limit from expensive gas and logical swap failures before changing wallet settings.
Establish where swap output went and what recovery depends on when the recipient differs from your intended account.
Check wallet activity when a mobile swap stops updating after you return from the signing app.
Check the recipient, token contract, network and hidden-token display when a confirmed swap seems to have produced no output.
Why token-level deductions can make a quote inaccurate or a router incompatible, even when you approve enough.
Why a wallet can connect to an aggregator yet fail when the application requests a transaction or typed-data signature.
Diagnose a minimum-output failure and compare a refreshed quote before accepting a wider execution range.
Work out whether a swap stopped before signing, failed during submission or lost its confirmation display before retrying.
Check supported chains and connection permissions when the wallet cannot switch to the network required by a swap.
Distinguish contract execution deadlines from pending transaction status and avoid resubmitting expired swap data.
Check the token pull step when a swap fails with TRANSFER_FROM_FAILED or a related transfer error.
What a user-rejected wallet request means and why earlier approvals or broadcasts still need checking.
Understand the evidence contained in a failed EVM receipt and the additional information needed to diagnose a swap.
Try a shorter phrase or give the topic filter a little more room.