billing
GET /v1/payment-methods
List the stored payment methods in scope.
Authentication
Send an API key as a bearer token. The endpoint checks billing.view; a key without it is refused with 403, not 404.
Where your organisation id goes
This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/payment-methods \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Returns the caller's stored mandates. Revoked methods are omitted. The gateway-side customer_ref/method_token are never returned — they are the references a charge is made against (CLAUDE.md §2.4).
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
org_id (query) | Uuid | No | Narrow the list to one organization. Without it the response is every organization the caller can read, and PaymentMethod carries no org_id, so a reseller or agency cannot… |
cursor (query) | string | No | Opaque cursor from a previous page's page.next_cursor. |
limit (query) | integer | No | Maximum items to return (page size). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | PaymentMethod[] | Yes | — |
page | PageMeta | Yes | — |
Errors this endpoint can return
401 · 403 · 429