Transfer-Tax Tokens: Sent Amount and Received Amount Can Differ

A token can implement transfer behavior that deducts part of an amount or directs some units elsewhere. This token-level mechanism needs separate investigation from the network fee for executing a transaction.

Distinguish the three cost locations

A network fee pays for chain processing in the relevant fee currency. An interface fee follows the application’s disclosed policy. A transfer-tax mechanism operates inside a particular token’s contract logic. These can coexist and should not be combined under an unexplained fee label. Start from the exact asset contract and provider documentation rather than assuming a discrepancy is caused by the wallet or by gas.

Use a clearly hypothetical example

Imagine a token whose documented transfer rule deducts two units from a 100-unit movement, leaving 98 for the recipient. That arithmetic describes a token rule, not RunixCoin’s interface fee or any verified supported asset. The actual mechanism could depend on sender, recipient or contract state. A quoted quantity based on ordinary ERC-20 assumptions may not represent the final recipient balance when those assumptions are wrong.

Check protocol-specific compatibility

Uniswap v3 documentation states that fee-on-transfer tokens do not work with its router contracts. This is version-specific integration guidance; a token appearing in an application’s search list does not supersede it. Do not increase slippage repeatedly as a substitute for understanding an unsupported mechanism. A higher tolerance does not establish that contract accounting, routing and user protections correctly handle a token’s transfer rules.

Collect evidence without retrying a payment

If reviewing an existing transaction, compare its receipt, identified token events and recipient balance at relevant blocks. Record the documented deduction rule and separate all other costs. Avoid sending another transfer merely to see whether the deduction repeats. RunixCoin’s public quote flow does not enable execution and this page does not certify transfer-tax tokens. An unresolved difference belongs in a factual report with public evidence, without private keys or signed payloads.

References and verification

Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.