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.
imtoken Knowledge

Token Approvals

A practical guide to token approvals with clear concepts, user checks and risk boundaries before wallet actions are confirmed.

On this page
  1. What an approval is
  2. Allowance scope
  3. Check the spender
  4. Revoke unused approvals

What an approval is

What an approval is is an essential part of understanding Token Approvals. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

What an approval is is an essential part of understanding Token Approvals. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Practical checks

  • Confirm the current account and network
  • Never share a seed phrase, private key or verification code
  • Read the full transfer, signature or approval request before confirming

Allowance scope

Allowance scope is an essential part of understanding Token Approvals. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Allowance scope is an essential part of understanding Token Approvals. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear

Check the spender

Check the spender is an essential part of understanding Token Approvals. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Check the spender is an essential part of understanding Token Approvals. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear

Revoke unused approvals

Revoke unused approvals is an essential part of understanding Token Approvals. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Revoke unused approvals is an essential part of understanding Token Approvals. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear