Fee-on-Transfer Token
Pronunciation: FEE ahn TRANS-fer TOH-kun
Definition
A fee-on-transfer token deducts a fee, tax, burn, reflection, or redistribution amount whenever tokens move between addresses. The recipient receives less than the nominal transfer amount or another balance change occurs during the transaction. This behavior can break payment, exchange, bridge, lending, and accounting integrations that assume ordinary ERC-20 transfers.
Overview
Meaning and scope
A fee-on-transfer token deducts a fee, tax, burn, reflection, or redistribution amount whenever tokens move between addresses. The recipient receives less than the nominal transfer amount or another balance change occurs during the transaction. This behavior can break payment, exchange, bridge, lending, and accounting integrations that assume ordinary ERC-20 transfers.
Mechanism and operation
The token contract modifies transfer logic so part of the amount is sent to a treasury, burned, distributed to holders, added to liquidity, or used for another purpose. The fee can be fixed, dynamic, address-specific, or controlled by an administrator. A user can submit a transfer of 100 tokens while the recipient receives 95. Decentralized exchanges need router functions that support fee-on-transfer behavior, and some protocols reject these assets entirely. Fees can also apply only to buys, sells, or selected addresses. Whitelisted accounts can avoid the fee, creating unequal market behavior. An administrator can sometimes raise the tax dramatically and prevent holders from selling, a common malicious-token pattern.
Practical payment example
A payer sends one hundred units, but transfer-tax logic delivers fewer to the merchant. The checkout measures the actual received amount before marking the invoice paid.
Operational checks
Balance-reflection mechanisms can change holdings without ordinary transfer events. Applications should simulate transfers, inspect contract code and roles, verify maximum configurable fees, and record actual received amounts. Fee-on-transfer design can fund a project or reduce supply, but it reduces composability and predictability. Deposit systems should either reject these tokens or credit only the observed balance increase after canonical confirmation.
Distinctions and limits
Payment systems that credit the requested amount rather than the actual increase create accounting losses. A token that follows the ERC-20 interface can still behave very differently from a standard fungible transfer.
Related reading
Related definitions: token contract, Token-2022.
Example
A payer sends one hundred units, but transfer-tax logic delivers fewer to the merchant. The checkout measures the actual received amount before marking the invoice paid.
Comparison
Payment systems that credit the requested amount rather than the actual increase create accounting losses. A token that follows the ERC-20 interface can still behave very differently from a standard fungible transfer. Related products such as Token-2022 should not be grouped automatically with Fee-on-Transfer Token.
Key Takeaway
Fee-on-transfer tokens change the amount received or redistribute value, requiring balance-based accounting, contract review, and integration-specific support.
Sources
- Ethereum ERC Standards — Ethereum Foundation (2026-08-01)
- Ethereum Documentation: Smart Contracts — Ethereum Foundation (2026-08-01)