imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.

Support

Support: Start with On-chain Facts Before Seeking Help

imtoken support content provides self-service troubleshooting and does not ask users to submit seed phrases, private keys, or wallet verification codes through a website. For asset, transfer, network, or DApp issues, start with non-sensitive facts such as the network, public address, and transaction hash.

Do not submit sensitive information

Seed phrases, private keys, and verification codes are not troubleshooting details.

Asset Not Displaying

Asset Not Displaying is best treated as a verification point rather than a background detail.

Practical checks for asset not displaying

For troubleshooting, collect non-sensitive facts first: the network, public address, transaction hash, and visible error message. Seed phrases, private keys, and verification codes are not support credentials, and unknown helpers should not be given remote control of a device.

A transaction hash is one of the most useful links back to on-chain facts. On the correct block explorer it can reveal sender, recipient, execution result, block height, gas usage, and confirmation progress. Keeping the hash is more useful for troubleshooting than relying on a screenshot alone.

The selected network determines which blockchain state receives the transaction. Similar names, matching address formats, or EVM compatibility do not make networks interchangeable. Before a transfer, contract call, or bridge operation, confirm that the wallet and destination service support the same network.

Working principle: When dealing with asset not displaying, proceed only when the request matches your intended action. If the details do not match, cancel and verify again.

Transaction Pending

When working with transaction pending, focus on what can be confirmed before you approve an action.

Practical checks for transaction pending

A transaction hash is one of the most useful links back to on-chain facts. On the correct block explorer it can reveal sender, recipient, execution result, block height, gas usage, and confirmation progress. Keeping the hash is more useful for troubleshooting than relying on a screenshot alone.

For troubleshooting, collect non-sensitive facts first: the network, public address, transaction hash, and visible error message. Seed phrases, private keys, and verification codes are not support credentials, and unknown helpers should not be given remote control of a device.

The selected network determines which blockchain state receives the transaction. Similar names, matching address formats, or EVM compatibility do not make networks interchangeable. Before a transfer, contract call, or bridge operation, confirm that the wallet and destination service support the same network.

Working principle: When dealing with transaction pending, proceed only when the request matches your intended action. If the details do not match, cancel and verify again.

DApp Connection Issues

The practical value of understanding dapp connection issues is that it reduces ambiguity during real wallet use.

Practical checks for dapp connection issues

Connecting a DApp establishes a session; it does not approve everything that follows. A connected site may still request a message signature, transaction signature, token approval, or network switch. Treat each request as a separate decision and verify its source and purpose.

For troubleshooting, collect non-sensitive facts first: the network, public address, transaction hash, and visible error message. Seed phrases, private keys, and verification codes are not support credentials, and unknown helpers should not be given remote control of a device.

A transaction hash is one of the most useful links back to on-chain facts. On the correct block explorer it can reveal sender, recipient, execution result, block height, gas usage, and confirmation progress. Keeping the hash is more useful for troubleshooting than relying on a screenshot alone.

Working principle: When dealing with dapp connection issues, proceed only when the request matches your intended action. If the details do not match, cancel and verify again.

Suspicious Support Contacts

For suspicious support contacts, the safest workflow separates what the interface shows from what the blockchain actually records.

Practical checks for suspicious support contacts

For troubleshooting, collect non-sensitive facts first: the network, public address, transaction hash, and visible error message. Seed phrases, private keys, and verification codes are not support credentials, and unknown helpers should not be given remote control of a device.

A transaction hash is one of the most useful links back to on-chain facts. On the correct block explorer it can reveal sender, recipient, execution result, block height, gas usage, and confirmation progress. Keeping the hash is more useful for troubleshooting than relying on a screenshot alone.

The selected network determines which blockchain state receives the transaction. Similar names, matching address formats, or EVM compatibility do not make networks interchangeable. Before a transfer, contract call, or bridge operation, confirm that the wallet and destination service support the same network.

Working principle: When dealing with suspicious support contacts, proceed only when the request matches your intended action. If the details do not match, cancel and verify again.

Prepare Safe Troubleshooting Details

Use prepare safe troubleshooting details as a checkpoint: identify the network, the intended action, and the information you can independently verify.

Practical checks for prepare safe troubleshooting details

For troubleshooting, collect non-sensitive facts first: the network, public address, transaction hash, and visible error message. Seed phrases, private keys, and verification codes are not support credentials, and unknown helpers should not be given remote control of a device.

A transaction hash is one of the most useful links back to on-chain facts. On the correct block explorer it can reveal sender, recipient, execution result, block height, gas usage, and confirmation progress. Keeping the hash is more useful for troubleshooting than relying on a screenshot alone.

The selected network determines which blockchain state receives the transaction. Similar names, matching address formats, or EVM compatibility do not make networks interchangeable. Before a transfer, contract call, or bridge operation, confirm that the wallet and destination service support the same network.

Working principle: When dealing with prepare safe troubleshooting details, proceed only when the request matches your intended action. If the details do not match, cancel and verify again.