Native Asset Payment

Overview

Meaning and boundaries

A native asset payment is a payment made with the blockchain’s built-in currency rather than with a token issued by a smart contract on that network. Native asset payments transfer the network’s built-in coin rather than a token defined by a separate asset contract. The asset can also be needed for transaction fees, and the transaction receipt and execution behavior may differ from those of smart-contract token transfers.

How it works in practice

Native assets are used directly by the protocol for value transfer and usually for transaction fees. Examples include BTC on Bitcoin and ETH on Ethereum. Monitoring reads native-value transfers rather than token transfer events. The checkout should distinguish the native asset from wrapped or tokenized versions, validate the network, account for gas or miner fees, and avoid requiring a token contract address. Asset identifiers should remain explicit in APIs and reports. An ETH invoice on Ethereum is a native asset payment, while a WETH transfer on Ethereum is a token payment even though the assets may track similar value.

Checks and failure points

Clarify the network, address type, exact unit and fee funding. On account-based chains, sending native value to a contract can trigger execution; on UTXO chains, payments are represented by outputs and spending conditions.

Operational evidence and decisions

Native and token balances should be distinguished in ledger and support interfaces. A wallet can hold the correct token yet lack native coin for gas, preventing token spending; a native-asset payment directly spends the protocol coin. Monitoring must identify the correct transaction type and exclude unrelated value transfers or execution side effects.

How it differs from related terms

Native-asset payment moves the chain’s protocol coin; token payment moves an asset issued through a token standard or contract. Related entries: Invoice Token Contract; Invoice Payment Asset; Network-Specific Payment Asset.