transaction-fee
API reference for configuring the transaction-fee token feature so the platform deducts per-operation fees on chain for mint, burn, and transfer.
The transaction-fee token feature deducts a configured percentage fee from each mint, burn, or transfer operation, crediting the deducted amount to a configured recipient. It is mutually exclusive with transaction-fee-accounting.
For the operator how-to, see Transaction fee how-to. For the architecture model, see Transaction fee architecture.
Configuration during token creation
{
"transaction-fee": {
"mintFeeBps": 100,
"burnFeeBps": 100,
"transferFeeBps": 50,
"recipient": "0x..."
}
}| Parameter | Type | Required | Description |
|---|---|---|---|
mintFeeBps | Integer | Yes | Mint fee in basis points. Zero suppresses mint-fee collection. |
burnFeeBps | Integer | Yes | Burn fee in basis points. |
transferFeeBps | Integer | Yes | Holder-initiated transfer fee in basis points. |
recipient | Ethereum address | Yes | Wallet that receives collected fees in the asset's own units. |
Behaviour
The platform deducts the fee from the operation amount before crediting the holder. A 100-unit mint with mintFeeBps: 100 credits 99 units to the holder and 1 unit to recipient.
Reading collected fees
GET /api/v2/token/{address}/features/transaction-feeReturns the configured rates, recipient, and aggregate collected balance per operation type.
Updating parameters
Restricted-mutable. Update through the governance-update path:
PUT /api/v2/token/{address}/features/transaction-fee
{
"transferFeeBps": 25
}Related
- transaction-fee-accounting — mutually exclusive variant.
- Feature constraints
aum-fee
API reference for configuring the aum-fee token feature and reading or collecting accrued management fees through dapi endpoints.
transaction-fee-accounting
API reference for configuring the transaction-fee-accounting token feature so the platform records per-operation fee accruals on chain without on-chain deduction.