# Create gateway URL: https://docs.hanzo.ai/docs/openapi/billing/post-billing-crypto-gateway > Takes a signed USDC payment from the caller's Circle Gateway balance to the treasury, and answers what became of it. `POST /v1/billing/crypto/gateway` > [Billing →](https://docs.hanzo.ai/docs/openapi/billing) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides) | | | | ------------- | ------------------------------------------------ | | **Address** | `https://api.hanzo.ai/v1/billing/crypto/gateway` | | **Method** | `POST` | | **Operation** | `post_billing_crypto_gateway` | | **Auth** | `Authorization: Bearer $HANZO_API_KEY` | Takes a signed USDC payment from the caller's Circle Gateway balance to the treasury, and answers what became of it. accepted: Circle Gateway LOCKED the USDC and the caller is credited — or, once the caller holds $1,000 of credit Gateway has not confirmed, credited when Gateway confirms this payment (deferred). pending: the outcome is not known yet; read it back or present the same payment again — it resolves to one credit either way. A refusal is 4xx with Gateway's reason (insufficient\_balance, invalid\_signature, …) or ours (nonce\_not\_issued, recipient\_mismatch, amount\_below\_minimum, …); 503 means the rail is shut. Who is credited is the caller, never a body value: the payer is resolved server-side, and the payment's own nonce must be the one issued to it. A named handler, not a closure, so zipdoc can lift this prose into the registry. ## Request 10 fields, body `application/json` (required). | Field | In | Type | Required | Description | | --------------------------- | ---- | ---------------------------- | -------- | -------------------------------------------------------------------------------------------------------- | | `authorization` | body | billing.GatewayAuthorization | — | | | `authorization.from` | body | string | — | | | `authorization.nonce` | body | string | — | | | `authorization.to` | body | string | — | | | `authorization.validAfter` | body | string | — | | | `authorization.validBefore` | body | string | — | | | `authorization.value` | body | string | — | | | `network` | body | string | — | Network is the CAIP-2 network the payment was signed for, one of the terms' accepts, e.g. "eip155:8453". | | `salt` | body | string | — | Salt is the salt the terms issued with the nonce. | | `signature` | body | string | — | Signature is the 65-byte EIP-712 signature, 0x hex. | ## Response | Status | Body | Meaning | | --------- | ---------------------- | ------- | | `200` | billing.GatewayPayment | ok | | `default` | problem-details | refused | `200` body — 13 fields. | Field | In | Type | Always | Description | | ------------- | ---- | --------------- | ------ | ----------- | | `amountCents` | body | integer (int64) | — | | | `createdAt` | body | string | — | | | `credited` | body | boolean | — | | | `deferred` | body | boolean | — | | | `from` | body | string | — | | | `id` | body | string | — | | | `network` | body | string | — | | | `payment` | body | string | — | | | `reason` | body | string | — | | | `status` | body | string | — | | | `txHash` | body | string | — | | | `updatedAt` | body | string | — | | | `value` | body | string | — | | Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors). ## Examples **CLI** ```bash hanzo billing crypto gateway create ``` **SDK** **.ts** ```ts import { Configuration, BillingApi } from 'hanzoai'; const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY })); const { data } = await api.postBillingCryptoGateway({ authorization: {"from":"","nonce":"","to":"","validAfter":""}, network: "" }); ``` **.py** ```python from hanzoai.cloud import ApiClient, Configuration from hanzoai.cloud.api import BillingApi client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"])) result = BillingApi(client).post_billing_crypto_gateway(authorization={"from":"","nonce":"","to":"","validAfter":""}, network="") ``` **.go** ```go cfg := hanzoai.NewConfiguration() cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY")) client := hanzoai.NewAPIClient(cfg) resp, _, err := client.BillingAPI.PostBillingCryptoGateway(context.Background()).Execute() if err != nil { return err } ``` **.rs** ```rust use hanzo_client::apis::{configuration::Configuration, billing_api}; let mut cfg = Configuration::new(); cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok(); let result = billing_api::post_billing_crypto_gateway(&cfg, Default::default()).await?; ``` **.java** ```java import ai.hanzo.cloud.ApiClient; import ai.hanzo.cloud.api.BillingApi; ApiClient client = new ApiClient(); client.setBearerToken(System.getenv("HANZO_API_KEY")); var result = new BillingApi(client).postBillingCryptoGateway(); ``` The method above is the one at the current release of the document. `hanzoai@8.5.914` (npm) and `hanzoai@8.5.914` (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. [SDKs →](https://docs.hanzo.ai/docs/sdks) **HTTP** ```bash curl -X POST https://api.hanzo.ai/v1/billing/crypto/gateway \ -H "Authorization: Bearer $HANZO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "authorization": { "from": "", "nonce": "", "to": "", "validAfter": "" }, "network": "" }' ``` **MCP** MCP reaches **billing** through the `billing` tool, which names its 45 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them: ```bash curl -X POST https://api.hanzo.ai/v1/mcp \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "describe", "arguments": { "op": "list_billing_accounts" } } }' ``` --- [Billing API](https://docs.hanzo.ai/docs/openapi/billing) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)