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.
Home / Send & Receive
imtoken

Send & Receive

Send & Receive: practical guidance with network, transaction, permission and security checks.

Before you begin

Send concepts

For Send & Receive, this section connects Send concepts with Send workflow. Before starting, confirm the active account, network and destination, then prepare the address, amount or contract information you expect to see. Never type a seed phrase, private key, recovery phrase or verification code into an unfamiliar site.

In practical use, Send verification should not be evaluated separately from Send risk. During the flow, treat connecting, signing, approving and sending as separate actions. Read each request in context, and cancel anything you cannot interpret until the source and purpose are clear.

Treat Send management as part of a repeatable review routine. After the action, review transaction history or the correct block explorer and remove connections or approvals you no longer need. If something looks wrong, stop additional signatures or transfers first. This helps turn visible information into verified information.

Complete the flow step by step

Send workflow

For Send & Receive, this section connects Send workflow with Send verification. Before starting, confirm the active account, network and destination, then prepare the address, amount or contract information you expect to see. Never type a seed phrase, private key, recovery phrase or verification code into an unfamiliar site.

In practical use, Send risk should not be evaluated separately from Send management. During the flow, treat connecting, signing, approving and sending as separate actions. Read each request in context, and cancel anything you cannot interpret until the source and purpose are clear.

Treat Send concepts as part of a repeatable review routine. After the action, review transaction history or the correct block explorer and remove connections or approvals you no longer need. If something looks wrong, stop additional signatures or transfers first. This helps turn visible information into verified information.

Common mistakes and troubleshooting

Send verification

For Send & Receive, this section connects Send verification with Send risk. Before starting, confirm the active account, network and destination, then prepare the address, amount or contract information you expect to see. Never type a seed phrase, private key, recovery phrase or verification code into an unfamiliar site.

In practical use, Send management should not be evaluated separately from Send concepts. During the flow, treat connecting, signing, approving and sending as separate actions. Read each request in context, and cancel anything you cannot interpret until the source and purpose are clear.

Treat Send workflow as part of a repeatable review routine. After the action, review transaction history or the correct block explorer and remove connections or approvals you no longer need. If something looks wrong, stop additional signatures or transfers first. This helps turn visible information into verified information.

Post-action review

Send risk

For Send & Receive, this section connects Send risk with Send management. Before starting, confirm the active account, network and destination, then prepare the address, amount or contract information you expect to see. Never type a seed phrase, private key, recovery phrase or verification code into an unfamiliar site.

In practical use, Send concepts should not be evaluated separately from Send workflow. During the flow, treat connecting, signing, approving and sending as separate actions. Read each request in context, and cancel anything you cannot interpret until the source and purpose are clear.

Treat Send verification as part of a repeatable review routine. After the action, review transaction history or the correct block explorer and remove connections or approvals you no longer need. If something looks wrong, stop additional signatures or transfers first. This helps turn visible information into verified information.

Risk note

Third-party DApps and smart contracts can introduce risk. Review permissions and remove approvals you no longer need.