Hanzo
OpenapiBilling

Save a card or account for the caller — POST /v1/billing/portal/methods

Vaults the instrument at the processor and stores the row.

POST /v1/billing/portal/methods

Addresshttps://api.hanzo.ai/v1/billing/portal/methods
MethodPOST
Operationpost_billing_portal_methods
AuthAuthorization: Bearer $HANZO_API_KEY

Vaults the instrument at the processor and stores the row.

A saved method is a card or account VAULTED at the processor: what is stored here is the processor's token for it plus the last four digits and the expiry a customer recognises it by, never a card number.

The list is the caller's OWN — the wallet this request bills from, resolved server-side — so a query cannot widen it to another customer of the same org.

/v1/billing/portal/methods answers the same list under the name a hosted checkout addresses it by. One set of rows, two spellings; a card added at either is present at both.

Saving a card ALREADY on file answers with the row that already holds it rather than stacking a duplicate — 200 for that, 201 for a genuinely new row, so a client can tell which happened. A card the processor declines is 402 and nothing is stored.

Request

The document declares no body for POST /v1/billing/portal/methods. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_billing_portal_methods, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo billing portal methods create

Billing API · All Hanzo APIs · Interactive reference

How is this guide?

On this page