billing

GET /v1/payment-methods

List the stored payment methods in scope.

All billing endpoints

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

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

NameTypeRequiredWhat it is
org_id (query)UuidNoNarrow 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 t…
cursor (query)stringNoOpaque cursor from a previous page's `page.next_cursor`.
limit (query)integerNoMaximum items to return (page size).

Response

NameTypeRequiredWhat it is
dataPaymentMethod[]Yes
pagePageMetaYes

Errors this endpoint can return

401 · 403 · 429