Skip to main content
Once buyers start paying, Crevio gives you the read-and-act surface for the money side: subscriptions, invoices, refunds, and the order record behind every purchase. Subscriptions and orders are largely read models you act on; invoices and refunds you create. You can ask Crevio to “pause Jane’s subscription until next month” or “refund order ord_abc123” and the agent calls the same endpoints below. For automated billing flows, you’ll call them directly.

Subscriptions

A subscription (sub_...) is created when a buyer pays for a subscription price variant. You don’t create subscriptions over the API — you list, retrieve, and change their state.

List and retrieve

Change subscription state

Each lifecycle action is its own POST sub-route:
ActionEndpoint
CancelPOST /subscriptions/{id}/cancel
PausePOST /subscriptions/{id}/pause
ResumePOST /subscriptions/{id}/resume

Invoices

An invoice (inv_...) is a request for payment you send to a customer. Create one, then the customer pays it by opening a checkout.

Create an invoice

FieldNotes
customerThe customer id (cus_...) being billed.
customer_name / email_addressRecipient details for the invoice.
price_variantThe price variant (price_...) this invoice charges for.
descriptionFree-text line shown on the invoice.
due_atWhen payment is due (date-time).

Pay an invoice

Paying an invoice goes through a checkout — pass the invoice id as the invoice param:
The returned checkout URL is what the customer uses to pay. See Checkouts.

Void an invoice

To cancel an unpaid invoice:
Invoice lifecycle is observable via webhooks: invoice.created, invoice.paid, invoice.past_due, and invoice.voided.

Refunds

A refund returns money on an existing order. The only required field is the order; omit amount for a full refund, or pass an amount in cents for a partial one.

Full refund

Partial refund

amount: 2000 refunds $20.00 of the order. The optional reason and notes are recorded with the refund. Refunds are also listable and retrievable, and emit refund.created / refund.updated webhooks.

Orders (the read model)

An order (ord_...) is the record of a completed purchase. You don’t create orders directly — they appear when a checkout is paid. Orders are made of order items (ordi_...), one per price variant purchased, and carry a charge (ch_...) for the payment.
Use the expand query param to inline related resources (e.g. customer) that otherwise appear as bare id strings. Individual line items are also retrievable directly via the order items endpoints.
The reliable signal that a sale is final is the order.paid webhook — fulfill purchases there rather than at checkout creation, since a created checkout isn’t yet a paid order.

Next steps

Checkouts

Create the checkouts that produce orders and pay invoices.

Products & pricing

Configure subscription and payment-plan price variants.

Webhooks

Subscribe to order.paid, invoice.paid, refund.created, and more.

Commerce overview

See how subscriptions, invoices, and refunds fit the whole model.