Token Transfer

Overview

Token Transfer is usually a contract or program operation. On an EVM network, an ERC-20-style transfer calls a token contract that updates its internal balance mapping. The transaction itself is paid with the network’s native asset, while the token amount is encoded in calldata.

Many indexers identify transfers from a standard Event Log, but the log should be tied to successful execution and the expected contract. Tokens can use proxies, fees, rebasing, hooks, blacklists, pauses, or nonstandard behavior. A familiar event signature does not guarantee ordinary economics.

Decimals affect display rather than the integer stored by the contract. A raw amount of one million units can represent one token or a much smaller value depending on metadata. Payment software must use the verified contract address and configured decimals, not merely a ticker symbol.

A token transfer differs from a Native Transfer. The recipient may receive the token while the sender pays gas in native currency, and the transaction’s top-level value field can be zero. Monitoring only native balance changes will miss most contract-managed transfers.

To credit a payment, systems should confirm the network, token contract, recipient, decoded amount, receipt status, and confirmation level. Complex cases may require a Transaction Trace or state query. Unsupported or fee-on-transfer tokens need explicit policy because the recipient’s net balance can differ from the requested amount.

Allowance-based transfers add another distinction: the transaction sender can be a router or spender contract while tokens move from a different owner. Payment attribution should therefore rely on the defined order and recipient relationship, not assume that `msg.sender`, the token `from` field, and the customer are always identical.