Crypto Invoice
Pronunciation: KRIP-toh IN-voys
Definition
A crypto invoice is a payment request that links a commercial obligation to a cryptocurrency or stablecoin amount, network, destination, and validity period. It can convert a fiat price into a crypto amount, provide a QR code or payment URI, and track detection, confirmation, expiration, and settlement. It differs from a conventional invoice because the blockchain payment instructions can expire or change with asset and exchange-rate conditions.
Overview
A crypto invoice is a payment request that links a commercial obligation to a cryptocurrency or stablecoin amount, network, destination, and validity period. It can convert a fiat price into a crypto amount, provide a QR code or payment URI, and track detection, confirmation, expiration, and settlement. It differs from a conventional invoice because the blockchain payment instructions can expire or change with asset and exchange-rate conditions.
Important control concerns include stale quotes, reused addresses, wrong networks, late and partial payments, transfer fees, duplicate payments, and invoice status diverging from blockchain state.
Systems should record invoice ID, order, fiat and crypto amounts, quote, asset, network, address, expiry, tolerance, transaction, status, and refund basis.
A complete record for Crypto Invoice should show where it depends on Payment URI and how it differs from E-Invoice. That distinction lets teams reconcile Crypto Invoice without treating a related interface or event as final financial evidence.
For Crypto Invoice, version control is essential. When Crypto Invoice interacts with Payment URI, corrections should use a replacement, credit note, cancellation, or auditable adjustment linked to the original record instead of overwriting historical values. In the relationship between Crypto Invoice and E-Invoice, exports and reports should reproduce the document as it existed at issuance, including the customer, tax rule, exchange-rate basis, payment terms, and payment instructions that were actually communicated.
Operational controls for Crypto Invoice should reconcile the requested balance with every accepted payment, fee, conversion, refund, write-off, and credit. When Crypto Invoice interacts with Payment URI, the system should distinguish document status from payment status, preserve who changed each field and why, and define how expired instructions, partial payments, excess payments, disputed items, and transactions received after cancellation are handled.
Key Takeaway
Crypto invoices require time-bound quotes, exact asset and network instructions, transaction matching, exception policy, settlement, and auditable order linkage.
Sources
- Peppol BIS Billing 3.0 — OpenPeppol (2026-08-01)
- OxaPay API Reference: Generate Invoice — OxaPay (2026-08-01)