Send & Receive

What to confirm before you begin

Verification focus

When working with Send & Receive, start by keeping receiving addresses, sending networks, and asset contracts in the same context. Turn receiving and sending into a repeatable verification process that keeps address, network, asset, amount and fees in one context. A familiar label or icon is not enough on its own; the active network, account, address, contract or transaction record should agree with the action you intend to take. For consequential actions, understanding exactly what is being requested matters more than moving quickly through a confirmation screen.

A practical Send & Receive workflow can follow a consistent sequence: confirm the source and destination, review asset contracts, then verify transfer amounts in the correct network context, and finally inspect gas fees together with the possible on-chain consequence. Only after that review should you sign or submit. Keep non-secret evidence such as a transaction hash or contract address so the result can be checked later.

The central risk around Send & Receive is that Wrong-network, wrong-address or wrong-asset transfers generally cannot be reversed by the wallet alone, so pre-signing checks matter more than recovery attempts. If an unexpected network switch, unfamiliar contract, excessive approval, changed address or urgency tactic appears, stop before confirming. Seed phrases, private keys and verification codes are never normal troubleshooting material; imtoken staff will not ask for them and they should not be submitted through websites, chats or remote-control tools.

Follow the main workflow in order

Key observations during the workflow

For “Follow the main workflow in order”, sending networks establishes the starting point, asset contracts helps explain whether the process is progressing as expected, and transfer amounts is often the detail that can be cross-checked against wallet history or public on-chain data. If those facts conflict, stop and verify the source again. Transfers, signatures, approvals and cross-layer actions deserve a complete review even when the interface looks familiar.

It also helps to separate interface information from verifiable on-chain facts. transfer amounts may describe the intent of an action and gas fees may provide useful status context, but important decisions should still be checked against transaction hashes and confirmations and the relevant network record. Wallet labels, token symbols, DApp copy and promotional language can all be imitated, so familiarity is not proof of authenticity.

When working with Send & Receive, start by keeping transaction hashes and confirmations, receiving addresses, and sending networks in the same context. Turn receiving and sending into a repeatable verification process that keeps address, network, asset, amount and fees in one context. A familiar label or icon is not enough on its own; the active network, account, address, contract or transaction record should agree with the action you intend to take. For consequential actions, understanding exactly what is being requested matters more than moving quickly through a confirmation screen.

The final review before signing or submitting

Verification focus

A practical Send & Receive workflow can follow a consistent sequence: confirm the source and destination, review asset contracts, then verify transfer amounts in the correct network context, and finally inspect gas fees together with the possible on-chain consequence. Only after that review should you sign or submit. Keep non-secret evidence such as a transaction hash or contract address so the result can be checked later.

The central risk around Send & Receive is that Wrong-network, wrong-address or wrong-asset transfers generally cannot be reversed by the wallet alone, so pre-signing checks matter more than recovery attempts. If an unexpected network switch, unfamiliar contract, excessive approval, changed address or urgency tactic appears, stop before confirming. Seed phrases, private keys and verification codes are never normal troubleshooting material; imtoken staff will not ask for them and they should not be submitted through websites, chats or remote-control tools.

For “The final review before signing or submitting”, receiving addresses establishes the starting point, sending networks helps explain whether the process is progressing as expected, and asset contracts is often the detail that can be cross-checked against wallet history or public on-chain data. If those facts conflict, stop and verify the source again. Transfers, signatures, approvals and cross-layer actions deserve a complete review even when the interface looks familiar.

• Review receiving addresses in the correct network context.
• Review sending networks in the correct network context.
• Review asset contracts in the correct network context.
• Review transfer amounts in the correct network context.
• Review gas fees in the correct network context.

How to respond when something looks wrong

Do not let urgency replace judgment

It also helps to separate interface information from verifiable on-chain facts. transfer amounts may describe the intent of an action and gas fees may provide useful status context, but important decisions should still be checked against transaction hashes and confirmations and the relevant network record. Wallet labels, token symbols, DApp copy and promotional language can all be imitated, so familiarity is not proof of authenticity.

When working with Send & Receive, start by keeping transaction hashes and confirmations, receiving addresses, and sending networks in the same context. Turn receiving and sending into a repeatable verification process that keeps address, network, asset, amount and fees in one context. A familiar label or icon is not enough on its own; the active network, account, address, contract or transaction record should agree with the action you intend to take. For consequential actions, understanding exactly what is being requested matters more than moving quickly through a confirmation screen.

A practical Send & Receive workflow can follow a consistent sequence: confirm the source and destination, review sending networks, then verify asset contracts in the correct network context, and finally inspect transfer amounts together with the possible on-chain consequence. Only after that review should you sign or submit. Keep non-secret evidence such as a transaction hash or contract address so the result can be checked later.

Records and follow-up checks after completion

Verification focus

The central risk around Send & Receive is that Wrong-network, wrong-address or wrong-asset transfers generally cannot be reversed by the wallet alone, so pre-signing checks matter more than recovery attempts. If an unexpected network switch, unfamiliar contract, excessive approval, changed address or urgency tactic appears, stop before confirming. Seed phrases, private keys and verification codes are never normal troubleshooting material; imtoken staff will not ask for them and they should not be submitted through websites, chats or remote-control tools.

For “Records and follow-up checks after completion”, receiving addresses establishes the starting point, sending networks helps explain whether the process is progressing as expected, and asset contracts is often the detail that can be cross-checked against wallet history or public on-chain data. If those facts conflict, stop and verify the source again. Transfers, signatures, approvals and cross-layer actions deserve a complete review even when the interface looks familiar.

It also helps to separate interface information from verifiable on-chain facts. asset contracts may describe the intent of an action and transfer amounts may provide useful status context, but important decisions should still be checked against gas fees and the relevant network record. Wallet labels, token symbols, DApp copy and promotional language can all be imitated, so familiarity is not proof of authenticity.