Use this file to discover all available pages before exploring further.
Invoicing is StablePay’s product for merchant-created, one-time invoices addressed to specific customers. It is built for B2B billing, services, wholesale orders, account-managed sales, and manual billing workflows where the merchant needs an official payable document and a clear payment record.Merchants create and manage invoices in the Merchant Portal, then deliver them by email, PDF, or hosted invoice page. The payer can review invoice details and pay through StablePay’s hosted payment experience when the invoice is open or past due.
Use Invoicing when the payment should be tied to a named customer and a specific bill.Common fit examples include:
B2B or wholesale orders where the buyer expects an invoice.
Professional services, retainers, and account-managed sales.
Manual billing flows where a finance or sales team creates the payment request.
Customer-specific amounts, due dates, notes, and line items.
Workflows that need invoice status tracking, reminders, PDFs, and recordkeeping.
If you need a public, reusable payment page that is not pre-bound to a customer, use Payment Links. If you need recurring billing, use Stablecoin Subscriptions.
The invoice is being prepared and is not yet payable.
open
The invoice is payable and can be sent or shared with the customer.
past_due
The invoice is still open, but its due date has passed and an unpaid amount remains.
paid
The invoice has been fully paid.
void
The invoice was canceled and is no longer payable.
past_due is a derived display state. It helps merchants understand overdue invoices without changing the underlying idea that the invoice remains open and unpaid.
The hosted invoice page is the payer-facing payment entry point for Invoicing. It lets the payer review merchant details, customer details, line items, amount due, due date, and payment state before starting payment.
Invoice state
Hosted page behavior
open
The payer can review details and pay.
past_due
The payer can still review details and pay, with overdue context visible.
paid
The page remains viewable for recordkeeping and receipt-style confirmation.
void
The page remains viewable for recordkeeping, but cannot be paid.
PDF invoice and receipt behavior can depend on invoice state. Open, past due, paid, and void invoices can remain useful as records, while payment receipt behavior is most relevant after successful payment.
Manual invoices are created by merchants for one-time customer billing workflows. They belong to the Invoicing product experience.Subscription-generated invoices are created by the subscription billing lifecycle. They may appear as billing records and can be useful for reporting, but they may be read-only in Portal invoice workflows because the subscription system controls their lifecycle.
