Definition and scope
How XRPL Token Transfer Fees Work addresses a distinct part of issued tokens and trust lines. Understand issuer-configured transfer rates and the transactions to which they apply.
Unlike native XRP, most fungible assets on XRPL represent obligations issued by an account. This category explains the trust relationships, flags, controls, and accounting conventions that make issued currencies and newer Multi-Purpose Tokens work. Issued assets depend on their issuer and must not be described as native XRP. Issuer controls apply only to eligible issued balances.
How it works
A classic issued-currency issuer can set a TransferRate that charges when value moves between parties other than the issuer. The rate affects path calculations and can change the source amount needed for delivery.
- TransferRate: verify this field, object, or component against the cited protocol documentation.
- issuer: verify this field, object, or component against the cited protocol documentation.
- SendMax: verify this field, object, or component against the cited protocol documentation.
- transfer fee: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A wallet quoting a token transfer reads the issuer's current TransferRate, estimates SendMax with liquidity and path costs, and confirms final source and destination changes from metadata.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
The transfer rate is not an XRP transaction fee and is not necessarily applied when the issuer is one side. Interfaces should disclose both network cost and issuer transfer effect.
Issued assets depend on their issuer and must not be described as native XRP. Issuer controls apply only to eligible issued balances.
Current network status
Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.