Crypto Invoice

Overview

An invoice is a promise to pay, not a payment

A crypto invoice says that a customer is expected to pay a specified amount for something. It does not mean that any transfer has happened. The invoice may specify a reference, accepted assets, available networks, a payment deadline and destination instructions. The blockchain knows none of the customer's order details unless the payment system provides a way to link them. The invoice identifier is therefore essential: it joins the store's commercial order to transfers later observed by the processor.

How the underlying system works

Invoice creation commonly converts the commercial amount into payment instructions for supported assets or networks. A request may return a hosted payment URL, an identifier and expiration information. The merchant must retain the invoice currency, requested value and effective exchange-rate or tolerance rules so that later transfers can be evaluated consistently.

An invoice has its own lifecycle. It may be awaiting payment, partly paid, fully paid, expired or refunded. A transfer arriving after expiry or in the wrong asset should not rewrite historical order data. Store the invoice ID, order ID and transaction references separately; reconciliation becomes difficult when all three are treated as one identifier.

Walk through the invoice lifecycle

A merchant creates invoice INV-204 for a $65 service and stores the returned tracking reference. The customer opens a payment page and chooses a supported token/network combination. The checkout supplies a destination and amount according to the rate and payment terms. The customer broadcasts a transfer. The processing service first sees evidence of that transfer, then decides whether amount, timing and confirmation conditions are met. If the transfer is smaller than requested, the invoice may remain underpaid or be accepted under a configured threshold. If money arrives after expiry, the processor needs a documented late-payment policy rather than silently changing the original invoice.

Keep three records distinct

The commercial invoice describes the obligation; the blockchain transaction records asset movement; the provider's payment record explains how the movement was applied to the obligation. One invoice can be associated with multiple transfers, and a transaction may contain multiple token movements. A store that records only a transaction hash often cannot explain partial payments or adjustments later. Use order ID, invoice/track ID and transaction evidence together. Before fulfillment, confirm the authoritative payment state through an authenticated integration rather than relying on the buyer's browser returning to a “success” URL.

Further reading and related concepts

Reference documents: OxaPay — Generate Invoice, OxaPay — Payment Status Table.

Related glossary topics: Crypto Payment Link, Crypto Payment Status, Underpayment Coverage.