A Solana Token-2022 transfer can debit 100 token units and add only 97 to the recipient’s spendable balance. If the mint charges a three-unit transfer fee, the destination token account records those three units in a separate withheld field. A Solana network fee is a separate SOL charge.
Which field tells you the rule, and which shows the withheld amount?
On the mint, TransferFeeConfig describes the fee rule. Its settings include a rate in basis points, a maximum fee, and the epoch when a configuration takes effect. A rate alone leaves out the cap and which configuration applied at the time.
On the destination token account, TransferFeeAmount tracks the withheld fee balance separately from the account’s normal token amount. It can include units from earlier transfers. The mint also has its own withheld accumulator, a different field on a different record. Read the destination account’s extension when comparing the destination before and after a transfer. Solana’s Token-2022 transfer fee reference explains both extensions.
One fictional transfer, three balance changes
Assume DEMO-MINT has zero decimals, so a raw unit is one displayed token unit. One successful transfer sends 100 units with a three-unit fee. These fictional before and after records use the same mint and accounts, with no other balance or withheld changes between observations.
| Record and field | Before | After | Change |
|---|---|---|---|
| Sender token amount | 500 | 400 | −100 |
| Destination spendable token amount | 20 | 117 | +97 |
| Destination withheld amount | 2 | 5 | +3 |
The sender’s 100-unit debit matches the 97-unit increase in the normal destination balance plus the three-unit increase in withheld tokens. The final withheld balance is five because two units were already there. Reading five as the fee for this transfer would overstate it by two.
If you only have the final withheld amount of five, the change in that field remains unknown. If an interface omits the extension, that view leaves the field unobserved. Compare records for the same mint, account and transfer, and account for any unrelated balance changes before attributing a difference to one transfer.
Where the SOL network fee shows up
The network charges its fee to the transaction’s designated fee payer in SOL, measured in lamports. The Solana fee structure reference describes that debit. Keep the SOL fee separate from the 100 token units in the example. They use different balances and units.
For a closer look at the records, see where Solana stores a token balance and how to identify the network fee payer. A Token-2022 transfer hook is another mint extension that can call a separate program. The fee and the hook answer different questions.
Sources
See something wrong? Brokzi logs material changes. Prepare a correction note.




