All guides

Wallet security

ERC20 approval versus transfer: what a crypto swap actually asks you to sign

Approve and send are different token operations. One can grant spending authority without moving the requested deposit; the other can transfer tokens without granting a continuing allowance. Recognizing the distinction helps you read a wallet prompt and avoid signing an unrelated action.

ETH coins with recognizable marks in a dark sculptural composition.
A spending authorization and a token payment are different wallet actions.

A direct transfer moves the token amount

An ERC20 transfer instructs the token contract to move units to a recipient. Your wallet presents a token amount and destination, while Ethereum gas is normally paid in ETH. The transaction should match the provider order's source token, chain, address and exact amount.

The contract address visible in a transaction's technical details may be the token contract executing the transfer, not the end recipient shown in the token-transfer record. Read the wallet's human-readable summary and verify the resulting token movement. Do not replace the deposit recipient with a token contract address because both appear somewhere in an explorer.

An allowance grants a spender authority

An approval establishes a token allowance for a spender. That is permission for a separate action to move tokens within the allowance under the token's rules; it is not automatically the transfer that funds a provider order. Approving a number and sending that number are distinct events.

The relevant fields are the token, chain, spender and allowance. A familiar application name or wallet logo does not verify the spender address. An unlimited allowance can expose more than the amount of a single intended transaction, so review what authority the actual operation requests rather than clicking through because an amount appears familiar.

How to choose the receiving network

Why some applications need approvals and this flow differs

A contract-based application may use an allowance so its contract can pull tokens for a particular interaction. Tornado Swap's ordinary provider flow instead displays a deposit address after order creation. You send the source asset from a wallet or exchange; a wallet connection is not required to create that address-based payment.

This is a description of the actual interface, not a claim that all approvals are malicious or that all address transfers are safe. Each workflow has its own checks. If another page asks for an approval while claiming it is required for this deposit, verify why that separate action is being introduced before signing.

A signature is not harmless because it has no gas fee

Some token systems use signed authorization messages, including permit-style arrangements, to grant permissions without a conventional approval transaction from the owner. A wallet prompt with no immediate gas charge can still carry meaningful authority. Read the message's purpose, chain, contract and requested scope.

Do not sign an unfamiliar message simply to view a quote, unlock a payout or speak to support. The address-based order process can be understood without granting wallet spending authority. If a prompt cannot be explained clearly by the action you intended, stop and inspect the source rather than treating a free signature as a risk-free click.

Worked example: USDC deposit versus allowance request

Imagine an order requests an illustrative 80 USDC on Ethereum to a generated provider address. The user opens their wallet's send function, selects USDC, enters that address and checks the exact amount and ETH gas. That transfer, when successfully confirmed and matched, is the source payment for the order.

Now imagine a different page requests unlimited USDC approval to an unrelated spender and calls it deposit verification. The approval does not itself prove that 80 USDC reached the provider. The user should not substitute it for the instructed transfer. They preserve the order and verify the separate request through the site's own support contact.

Review existing allowances as a separate task

If you have previously used contract applications, a wallet may hold old allowances. Reviewing them can be sensible wallet maintenance, but it is not a way to reverse a confirmed transfer or force a provider payout. Revocation changes future spending permission under the relevant token's rules.

Use a trusted wallet feature or carefully verified allowance tool and check the correct chain. A revocation can require its own network fee. Do not connect to an unsolicited link claiming your swap is blocked by an allowance or pay to unlock a balance. Keep this maintenance independent from the evidence for a funded provider order.

Review the difference between rate types

Failure and recovery have different meanings

A failed transfer does not necessarily mean no gas was spent, while a successful approval does not mean the deposit was paid. Check what operation actually reached the chain and its status. Support needs the deposit transfer record, not an unrelated allowance transaction presented as proof of payment.

If tokens were sent to an unintended address, changing an allowance afterward does not edit that transfer. If an allowance was granted to an unexpected spender, address that permission promptly using legitimate wallet controls and investigate whether tokens moved. Never share the wallet's seed phrase or private key with someone offering to repair either situation.

A signing checklist you can apply to any prompt

The table emphasizes the action, not just the button label. Before confirming, explain in plain words what the wallet will authorize or transfer, on which chain and for whose benefit. If that description differs from the provider's deposit instructions, resolve the mismatch first.

For the actual deposit, use the current order address, enter network and amount separately from its address-only QR, and save the swap ID plus transaction hash. Provider policies and possible verification are separate from wallet authority. A support request should be handled through the official contact path rather than a new contract signature demanded in a private message.

PromptPrimary question
TransferWhich token amount goes to which recipient?
ApprovalWhich spender gets which allowance?
Permit or messageWhat authority does this signature grant?
RevocationWhich existing permission changes on which chain?

A FEW MORE DETAILS

Common questions

Does approving a token pay my swap deposit?

Not by itself. An allowance and a token transfer are different operations. The provider needs the payment specified in its confirmed order.

Do I need a wallet connection for this deposit flow?

The ordinary Tornado Swap flow gives a provider address after order creation. You can pay it separately from your wallet or exchange.

Is an unlimited approval always required for a token send?

No. A direct wallet transfer is different from a contract interaction that uses an allowance. Review the actual workflow and requested spender.

Can I ignore a signature because it costs no gas?

No. A message can grant authority without an immediate on-chain fee. Read and understand the exact authorization before signing.

Prepared by Tornado Swap to explain the swap workflow. Network conditions and provider offers can change; check the current order instructions before sending funds.

Keep reading