
Fee-on-Transfer Tokens: Requested vs Received Amounts
Handle tokens that deduct transfer fees by separating requested amounts, actual recipient changes and the contract-specific evidence behind each value.
Read the guideIndexbase journal / ideas for builders
Explore activity over a range and holdings at a precise historical point.
Follow the article feed20 articles / page 2 of 2

Handle tokens that deduct transfer fees by separating requested amounts, actual recipient changes and the contract-specific evidence behind each value.
Read the guide
Decide how to handle zero-value token transfer events without confusing display filters, event identity, wallet ownership or economic activity.
Read the guide
Choose inclusive and exclusive date boundaries for wallet history, convert them to chain ranges, and avoid duplicates between adjacent reporting periods.
Read the guide
Define what first wallet activity means, distinguish discovery from coverage, and avoid treating a partial API response as a wallet creation date.
Read the guide
Normalise wallet addresses for comparison while preserving display checksums, network context and the different encoding rules of non-EVM chains.
Read the guide
Design reversible spam-token filters using explicit signals, without treating a token symbol, unsolicited transfer or logo as proof of trust.
Read the guide
Track network execution fees separately from transferred value, preserve failed-transaction costs, and avoid charging every transfer event the full fee.
Read the guide
Export wallet activity with stable IDs, exact quantities, time-zone clarity and safe spreadsheet handling, while preserving links to original records.
Read the guideThe editorial approach
Each guide starts with a concrete developer question and separates technical observations from the interpretation an application adds. Worked examples use illustrative values; references point to standards and technical documentation.
Published by Indexbase. Explore related guides as your requirements develop, from a first data question to a more deliberate integration workflow.