Hanzo
OpenapiBilling

Issues a deposit address the caller can send crypto to, on the asset they ask…

Issues a deposit address the caller can send crypto to, on the asset they ask for.

POST /v1/billing/crypto/deposit

Addresshttps://api.hanzo.ai/v1/billing/crypto/deposit
MethodPOST
Operationpost_billing_crypto_deposit
AuthAuthorization: Bearer $HANZO_API_KEY

Issues a deposit address the caller can send crypto to, on the asset they ask for.

The address credits the CALLER'S own wallet and nobody else's: the payer is the validated principal, never a body value. Asking again reuses the caller's open intent rather than minting a second address, so a refresh cannot spray key generations — and a payer who sent to the address they saw earlier is still credited.

No balance moves here. The chain watcher credits on real confirmations, so what comes back is an address and a status, not a receipt.

An asset this rail cannot mint on is 400 — ask for another. A rail that is shut for that asset is 503 — nothing sent now can be credited.

A named handler, not a closure, so zipdoc can lift this prose into the registry.

Request

3 fields, body application/json (required).

FieldInTypeRequiredDescription
amountCentsbodyintegerAmountCents is what the payer intends to send, for the record.
chainbodystringChain is the network to receive on.
tokenbodystringToken is the asset on that chain.

Response

StatusBodyMeaning
200CryptoDepositok

200 body — 7 fields.

FieldInTypeAlwaysDescription
addressTagbodystring
chainbodystring
depositAddressbodystring
expiresAtbodystring
idbodystring
statusbodystring
tokenbodystring

Failure carries the platform error shape — see Errors.

Examples

hanzo billing crypto deposit create

Billing API · All Hanzo APIs · Interactive reference

How is this guide?

On this page