Hanzo
OpenapiBilling

Add funds with a single-use card token

Charges a card token from the browser's payment SDK and credits the caller's prepaid wallet — the cold-customer path, where nothing has to be saved first.

POST /v1/billing/topup/token

Addresshttps://api.hanzo.ai/v1/billing/topup/token
MethodPOST
Operationpost_billing_topup_token
AuthAuthorization: Bearer $HANZO_API_KEY

Charges a card token from the browser's payment SDK and credits the caller's prepaid wallet — the cold-customer path, where nothing has to be saved first.

The wallet credited is the CALLER'S OWN, resolved from their signed identity. It is never a value in the request: a client-set selector is how a customer once topped up one account while their usage drew from another.

X-Idempotency-Key makes a retry safe. With one, a repeat replays the first result; without one, the same amount from the same subject inside a short window does too. The key reaches the processor as well as our own guard, so the charge is exactly-once at the gateway even if our guard store is down.

The amount is bounded server-side. A decline is 402 and nothing is credited.

Request

The document declares no body for POST /v1/billing/topup/token. 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_topup_token, 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 topup token

Billing API · All Hanzo APIs · Interactive reference

How is this guide?

On this page