Skip to main content
Ideal for: Billing a named customer for itemised work or goods — professional services, B2B orders, anything that needs a document with line items, tax and a due date. Create and send invoices without code on the merchant dashboard, or use the API below to automate it. Both send a customer a request to pay, but an invoice is a document and a payment link is a door. Use an invoice when the customer needs a document — something with your line items on it that they can file, forward to their finance team, or reconcile against a purchase order. Use a payment link when they just need to pay. Sending many invoices at once? See Bulk invoicing.

How it works

You post the customer, a due date and the line items. SeerBit calculates the total, assigns an invoice number, and emails the invoice to customerEmail with a payment link inside it. The customer pays through SeerBit’s hosted page, and you can look the invoice up at any time by its number, your order number, or the customer’s email — or re-send it if they lost it.

Authentication

Invoicing calls are authenticated with a bearer token, generated from your public and secret keys.

Authentication

How to generate the token, and which credential every other SeerBit API expects.

Creating and sending an invoice

For the full specification, see our API Reference POST

Request Sample

The code snippet below shows an example request for creating and sending an invoice All body parameters are required

Response Sample

The code snippet below shows an example response for creating and sending an invoice

Parameter description

All body parameters are required.
invoiceItems object
The invoice total is calculated from the line items; you do not send an amount.

Response fields

Re-send an Invoice

For the full specification, see our API Reference GET

Request Sample

Response Sample

The code snippet below shows an example response to resend an invoice

Get invoice by customer email

For the full specification, see our API Reference GET

Request Sample

Response Sample

The code snippet below shows an example response to get invoice by customer email

Get invoice by InvoiceNo

For the full specification, see our API Reference GET

Request Sample

Response Sample

The code snippet below shows an example response to get an invoice by invoice number

Get invoice by orderNo

For the full specification, see our API Reference GET

Request Sample

Response Sample

The code snippet below shows an example response to get an invoice by invoice order

Notes

  • Store the InvoiceNo you get back. It is how you re-send, look up or reconcile the invoice afterwards — InvoiceID is internal.
  • Tax is per line, not per invoice. Each item carries its own tax percentage, so mixed-rate invoices work without extra fields.
  • Re-sending does not create a new invoice. It emails the existing one again, so the invoice number and amount stay the same.
  • Confirm payment server-side before you treat an invoice as settled — see Verify a payment.
  • Invoices created with test keys only work in test mode. See Test and live modes.