Sabí writes each change for the people who need it, and checks every step before anyone reads it.
The change: customers can pay an invoice in parts.
LED-482The payments endpoint now accepts an amount lower than the balance. New status: partially_paid.
Backed by a ticket or changeCustomers can now pay in parts. If a customer asks why their invoice is still open, check Payment history.
Backed by a ticket or changeYou can pay an invoice in more than one payment. Your invoice stays open until it's fully paid.
Checked in the productFor your customers
When your product changes, the help centre article changes with it. Every step is tried in your product first, and customers only see what passed your approval rules.
Hosted by Sabí on your own address, such as help.yourproduct.com [or published into Zendesk or Intercom].
When a customer pays you, record it on the invoice so your books stay up to date. You can record the full amount or part of it.
For your team
Every release comes with a short summary of what changed and what to tell customers. Every sentence links to the ticket it came from.
What changed in Release 8.3
Shipped today · 4 changesCustomers can pay an invoice in parts.
What to tell customers: record each payment; the invoice stays open until it's fully paid.
2 pages updatedThe Mark as paid button is now called Record payment.
1 page updatedInvoices can show a new label: Partly paid.
Behind-the-scenes improvements to how invoices are stored. No pages affected.
Customers can now pay in parts. Use Record payment for each payment.
The invoice closes only when the full amount is paid.
For your developers
Endpoints, fields and behaviour, updated when the code changes. Only the parts that changed are rewritten.
Record a payment
Payments APIPOST /v1/invoices/{invoice_id}/payments
{ "amount": 250.00, "currency": "EUR" }Response{ "status": "partially_paid", "balance_due": 350.00 }Changed in 8.3: amount can be lower than the balance due. The invoice status becomes partially_paid.

Coming next: help centre articles tailored to each reader's role and plan.
Product documentation that writes itself, then checks itself.