Transfer-Fee Token Payment

Overview

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. 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. This differs from a blockchain network fee, which is paid to process the transaction. Related operational concepts include Unsupported Asset Payment, Accepted Cryptocurrency, and Crypto Invoice Matching. They should remain connected through identifiers and evidence without being treated as the same payment state, control, or financial result.

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. The authoritative record for Transfer-Fee Token Payment should also show the rule version, responsible system, permitted state transition, and any downstream action such as fulfillment, settlement, refund, or manual review.

In the same operational workflow, it should be interpreted alongside Unsupported Asset Payment , Accepted Cryptocurrency , and Crypto Invoice Matching ; these terms describe related stages or controls but are not interchangeable. Those details prevent the term from becoming a vague label and allow merchants, developers, finance teams, and risk teams to apply the same meaning.

Operational ownership for Transfer-Fee Token Payment should cover configuration changes, access, monitoring, customer treatment, accounting, and escalation. 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.