GET · Billing & invoices
The ways one invoice can be paid
The ways one invoice can be paid
/api/v1/invoices/{invoice}/payment-methods
Description
Returns {can:{…}, totalUnpaid, balance, autogiroEnabled, cards:[{id, brand, last4}]}. Call this before pay_invoice_with_card to pick a card_id, or pay_invoice_with_balance / pay_invoice_with_autogiro. Reads only — it moves no money.
Path parameters
| Name | Type | Description |
|---|---|---|
invoice
required
|
string |
Query parameters
| Name | Type | Description |
|---|---|---|
invoice_id
required
|
integer |
The numeric invoice id. Get it from list_invoices → data[].id.
|
Responses
The specification does not describe this response body; the note in the rail says what to expect.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.