Skip to main content
Nozle generates invoices from recurring charges, metered usage, one-off purchases, and subscription transitions.

​
Fees of deleted Features

Deleting a Feature in the middle of a billing period does not drop its fees. They stay in the minimum commitment true-up, in the invoice’s recurring breakdown, and in GET /fees?feature_code= (documented in the API reference). Before, the true-up over-billed the customer by those fees and the other two left them out.

​
Read invoices

Fetch invoices from your authenticated backend with GET /api/v1/invoices?customer_id={id}. Derive the customer from the logged-in user or workspace rather than browser input. The list holds the invoices Core’s API shows, other than drafts, so status is finalized, voided, failed or pending. Whether an invoice is paid is in payment_status: pending, succeeded (paid) or failed. invoice_type is subscription, add_on, credit, one_off, advance_charges or progressive_billing. See List Invoices.

​
Lifecycle

  1. Nozle calculates recurring and usage charges.
  2. The invoice is created according to the plan’s billing timing.
  3. Your connected payment provider, Stripe or Razorpay, collects payment when configured.
  4. Verified payment events update invoice and subscription state.
  5. The invoice PDF becomes available for customer delivery.

​
React applications

The current React SDK does not fetch customer invoices. Expose a narrow merchant endpoint and render the returned fields in your application.

​
Email delivery

Nozle Cloud manages transactional invoice delivery and sender infrastructure.

​
Further reading