Hosted Crypto Invoice
Pronunciation: HOH-stid KRIP-toh IN-voys
Also known as: Hosted Cryptocurrency Invoice, Hosted Invoice
Definition
A Hosted Crypto Invoice is an invoice displayed and managed on a provider-operated web page rather than rendered entirely by the merchant.
Overview
Context and purpose
The page can show amount, currency, line-item or description data, payment options, status, expiration, and receipt information. The merchant should treat the provider’s server-side invoice record as authoritative and verify payment independently from browser redirects. When implementing Hosted Crypto Invoice alongside Hosted Checkout, the invoice should remain distinct from its payment sessions so late transfers, refunds, credits, and exchange-rate changes do not rewrite the original commercial document. Hosted Crypto Invoices are useful for sharing payment requests through email, messaging, or customer portals without building a complete payment page. The provider can update available methods and security components centrally. The hosted page should use a trusted domain and clearly identify the merchant or recipient. The merchant must control which order and amount were used to create the invoice . Expiration, quote, underpayment, and confirmation status should be visible.
How it works
A hosted crypto invoice is a payment request displayed on a provider-hosted page rather than rendered entirely inside the merchant’s application. The provider may present the address, QR code, chain, amount and countdown while the merchant still owns the order lifecycle.
Practical checks and failure points
Confirm domain authenticity, signed or authenticated invoice identifiers, expiry behavior and how the merchant gets final payment status.
Related concepts
Example
A merchant generates a hosted invoice URL for a $75 purchase. The buyer pays from a wallet, and the merchant processes the result from verified server events instead of trusting the return redirect.
Comparison
Hosting changes the checkout interface; it does not by itself determine whether funds are custodial.
Key Takeaway
Confirm domain authenticity, signed or authenticated invoice identifiers, expiry behavior and how the merchant gets final payment status.
Sources
- Payment Request API — World Wide Web Consortium (2026-08-02)
- Quickstart: Receive Stablecoin Payins — Circle Developer Documentation (2026-08-02)
- Payment Processing — Bitcoin Developer Documentation (2026-08-02)
- Peppol BIS Billing 3.0 — OpenPeppol (2026-08-01)
- OxaPay API Reference: Generate Invoice — OxaPay (2026-08-01)