Why a Swapped Token May Need Manual Import
A cross-chain swap can finish while the destination wallet hides the received token; manual import adds its verified address to the wallet’s display, not the chain.
Merkle Street Newsroom#1fa3894 min read
Manual token import makes a swapped asset visible in a destination wallet by adding its token identifier on the correct chain. First, a swap service routes the trade from the source asset to a destination asset, sometimes across a bridge or other cross-chain route. The destination chain records the result. The wallet then reads that chain and shows balances for assets it knows how to display. If it does not list the received token, the balance can exist on-chain while the wallet’s screen looks empty.
That last step is a display issue, not another swap. Importing a token tells the wallet which asset to track; it does not transfer funds or change the transaction. A fuller walkthrough of a native BTC-to-ETH route appears in this thor swap guide. The same distinction matters after other cross-chain swaps: first establish where the transaction ended, then decide whether the wallet needs an asset entry.
Why does a swapped token not appear in my wallet?
A token can be on the destination chain without being in the wallet’s default asset list. Wallets often show common assets automatically and let users add others by identifier. The chain keeps the authoritative balance; the wallet provides an interface for viewing it. Think of the token list as a contact list: adding a contact makes it easier to find, but does not create the person or move them anywhere.
Cross-chain services may use different routes and settlement steps. A swap can involve a source-chain transaction, a bridge or routing mechanism, and a destination-chain transaction. Until the destination step completes, there may be no destination balance to display. A source-chain confirmation alone does not prove that the receiving asset has arrived. Check the swap’s status and destination transaction details before importing anything.
How do I import the received token safely?
Find the destination chain and the token’s identifier, then add it through the wallet’s asset or token-import screen. For many EVM-compatible chains, the identifier is a contract address. Other networks use a different identifier, such as a mint address. The identifier must match the destination network and the asset you received. A familiar token name or ticker is not enough because unrelated assets can use the same label.
- Confirm the destination network shown in the swap details.
- Find the destination transaction and verify that it completed.
- Get the token identifier from the swap details, a trusted project source, or the relevant chain explorer.
- Check that the wallet shows the expected asset and balance after import.
Wallet screens vary, but the usual flow is to select the network, choose an option such as “Import token,” enter or paste the identifier, and review the detected token before adding it. Some wallets fill in the name and decimal display automatically. Those labels help the wallet format the balance; they do not prove that the identifier is genuine. If the wallet cannot find the asset, recheck the network and identifier rather than trying addresses at random.
What should I check if the balance is still missing?
Compare the destination transaction with the wallet address you control. The transaction should show a completed transfer or swap to that address on the destination chain. If it does, check that the wallet is connected to that same chain and that you imported the exact token identifier. A wrong network can hide the balance even when the asset is present elsewhere.
Be especially careful with identifiers copied from unsolicited messages, search ads, or lookalike token pages. A malicious token can imitate a real asset’s name and symbol. Importing an identifier only adds it to the display, but interacting with a counterfeit asset or a site built around it can expose you to loss. For most readers, the better choice is to verify the destination transaction and identifier first, then import only if the wallet still omits the asset.
The key distinction is simple: the swap changes assets on-chain; manual import changes what the wallet displays. Check the destination record before treating a missing screen balance as a failed trade.