Transfer-Fee Token Payment

Overview

Meaning and scope

A transfer-fee token payment uses a token whose contract deducts, redirects, burns, or otherwise applies a fee during transfer. As a result, the amount received by the merchant can be lower than the amount entered or emitted as the nominal transfer value. The token contract executes its fee logic when the payer sends funds.

Mechanism and operation

Payment systems should allowlist such tokens only after contract-specific testing, reconcile the actual recipient balance, define whether the payer must gross up the amount, account for refunds and payouts that incur another fee, and monitor upgrades or parameter changes. Depending on implementation, the fee may be taken from the sent amount, charged additionally, distributed to holders, or varied by address and transaction conditions. For Transfer-Fee Token Payment, the exact deployed contract is the operational asset definition. This supports the central requirement that for fee-on-transfer tokens, payment completion must use the actual amount received, not only the transaction input or requested token amount.

Practical payment example

A buyer sends a token that deducts a transfer fee. The checkout measures the recipient’s actual balance increase instead of treating the gross transaction amount as the amount delivered.

Operational checks

Read the token mint or contract rules that actually apply at transfer time and measure the beneficiary’s net token delta. Test whether an approved transfer fee can later change. The invoiced amount, sent amount and received amount should be stored as separate fields to prevent hidden shortfalls.

Distinctions and limits

This differs from a blockchain network fee, which is paid to process the transaction. Those details prevent the term from becoming a vague label and allow merchants, developers, finance teams, and risk teams to apply the same meaning.

Related reading

Related definitions: Unsupported Asset Payment, Accepted Cryptocurrency.