Invoices

Invoices connect a customer, an amount due, and a payable collection experience.

Engineering flowBuild, verify, then reconcile

Test this flow in sandbox →

1. 01Create invoiceStore its ID with your internal order before sending it.
2. 02Send and collectGive the customer the supported payable experience.
3. 03Receive paymentA hosted redirect or email delivery is not payment proof.
4. 04Verify and fulfilReconcile the verified invoice/payment state before fulfilment.

Use a dashboard-issued sandbox API key on your server. Do not enter credentials into this documentation site.

Invoice lifecycle

Create invoice → review → send → customer pays → verified payment event → reconcile invoice state → fulfil

Store the returned invoice ID with your internal order. A sent email, hosted payment redirect, or customer claim is not proof of payment; only reconcile after the verified invoice/payment state is final.

Use Payment Links for hosted collections and the Invoices API reference for creation, sending, status, and lifecycle operations.