To verify a token before swapping on ParaSwap, confirm four things in order: the network, the token contract address, the token’s decimals, and the direction of the trade. Then compare the expected output with the asset you actually intend to receive. If any check fails, do not approve the token or sign the swap; a familiar ticker is not proof that the selected asset is correct.
Start with the selected network
A token symbol has meaning only within a specific blockchain. USDC on Ethereum, USDC on an L2, and a bridged version on another network may share the same ticker while using different contracts and having different liquidity.
Before checking the token itself, confirm that your wallet and the swap interface are set to the same network. Check the chain name and, where shown, its chain ID. Do not rely on the wallet’s currently selected network alone: a wallet can hold similarly named assets across several chains, while the swap route may use only one of them.
The network also determines the gas asset required to approve and execute the transaction. Keep enough of that chain’s native asset available. A correct token selection can still result in a failed transaction if the wallet cannot pay network gas.
Match the contract address, not just the ticker
Open the token details in the swap form and copy the contract address exactly as displayed. Compare it with an independent source, such as a reputable block explorer or the token issuer’s published documentation. Check every character at the beginning and end; a shortened address can conceal a mismatch.
If the same ticker appears more than once in the asset picker, treat the entries as different assets until their addresses are confirmed. This matters especially for native and wrapped assets, or for native and bridged stablecoins. A token name, logo, or decimal count is not sufficient evidence of identity.
If the asset pair or network still looks ambiguous, review the ParaSwap context before continuing so you understand how the selected token fits the swap. That broader context does not authenticate a contract address, so the address comparison remains a separate required check.
Check decimals and trade direction before approving
Decimals control how a token’s smallest units are interpreted. A token with six decimals represents one whole token as 1,000,000 base units; one with eighteen decimals represents it as 1,000,000,000,000,000,000 base units. A mismatch can produce incorrect amounts or cause an API-based transaction to fail.
Confirm that the source token is the asset you are spending and the destination token is the asset you expect to receive. For a sell order, the input amount is fixed and the output may vary. For a buy order, the desired output is fixed and the input requirement may change. Read the wallet confirmation with that distinction in mind.
Before granting an approval, check:
- The token being approved is the intended source asset.
- The network in the wallet matches the network in the swap.
- The spender address belongs to the transaction you deliberately initiated.
- The allowance is not larger than you are comfortable granting.
Use the quote as a consistency check
Once the address and direction are confirmed, inspect the quote for contradictions. The displayed output should be the expected asset, the amount should use a sensible number of decimals, and the estimated price impact or slippage should match the pair’s apparent liquidity.
A large price impact on a small trade, an unexpectedly wide slippage setting, or a route that changes after the token selection is a reason to pause. Refresh the quote and recheck the pair rather than repeatedly signing transactions. Quotes can change as market conditions and available liquidity change, so a displayed amount is not a guaranteed execution result.
Apply the stop rule to a concrete case
Suppose you intend to swap a stablecoin for ETH on an L2. The asset picker shows two entries with the same stablecoin ticker. One contract matches the address you verified; the other is a bridged variant. If the verified address is not the one selected in the quote, stop even if the logo and displayed balance look familiar.
The correct next action is to remove the ambiguous asset, select the verified contract on the correct network, refresh the quote, and inspect the approval again. If the wallet confirmation shows a different token, chain, spender, or destination asset than expected, reject the transaction. This four-part mismatch rule is more reliable than judging a swap by its headline exchange rate.