Native Asset Payment
Pronunciation: NAY-tiv AS-et PAY-muhnt
Definition
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 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. It differs from an ERC-20 or similar token payment, where the asset is identified by a contract and transferred through contract execution.
Overview
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. In an operational payment system, this field or policy should have one authoritative meaning across the API, checkout, webhook, ledger, and support tools.
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. In practice, the system should preserve the original request, the observed blockchain or checkout evidence, and every status change that affects this value. This makes support investigations and financial reconciliation possible without reconstructing the payment from screenshots or mutable client data.
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. The implementation should use exact asset precision, authenticated server-side updates, and idempotent processing wherever repeated API calls, blockchain observations, or webhook deliveries can occur.
It differs from an ERC-20 or similar token payment, where the asset is identified by a contract and transferred through contract execution. It should be interpreted alongside Invoice Token Contract, Invoice Payment Asset, Network-Specific Payment Asset. These concepts belong to the same workflow, but each answers a different operational question and should not be collapsed into one ambiguous field.
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. The practical test is whether a merchant can explain how the value was produced, verify it independently, and apply the same rule consistently when the payment is delayed, duplicated, partially paid, refunded, or reviewed manually.
Key Takeaway
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; its meaning and evidence must remain consistent across checkout, monitoring, fulfillment, and reconciliation.
Sources
- ERC-20: Token Standard — Ethereum Improvement Proposals (2026-08-02)
- ERC-7528: ETH (Native Asset) Address Convention — Ethereum Improvement Proposals (2026-08-02)
- Supported Currencies — OxaPay (2026-08-02)