# Get gateway

URL: https://docs.hanzo.ai/docs/openapi/billing/get-billing-crypto-gateway-by-id

> Reads one of the caller's own USDC top-ups back: pending, accepted (credited or deferred), settled, failed or refused.

`GET /v1/billing/crypto/gateway/{id}`

> [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/{id}` |
| **Method**    | `GET`                                                 |
| **Operation** | `get_billing_crypto_gateway_by_id`                    |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`                |

Reads one of the caller's own USDC top-ups back: pending, accepted (credited
or deferred), settled, failed or refused.

A payment belonging to another payer answers 404, exactly as an id that names
nothing, so a guessed id cannot confirm somebody else's payment exists.

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

## Request

1 field.

| Field | In   | Type   | Required | Description                           |
| ----- | ---- | ------ | -------- | ------------------------------------- |
| `id`  | path | string | yes      | ID is the top-up's id, from the path. |

## 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 get <id>
```

**SDK**

**.ts**

```ts
import { Configuration, BillingApi } from 'hanzoai';

const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBillingCryptoGatewayById({ id: 'id' });
```

**.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).get_billing_crypto_gateway_by_id(id='id')
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.BillingAPI.GetBillingCryptoGatewayById(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::get_billing_crypto_gateway_by_id(&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).getBillingCryptoGatewayById();
```

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 https://api.hanzo.ai/v1/billing/crypto/gateway/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

Tool `billing`, op `get_billing_crypto_gateway_by_id` — POST the JSON-RPC envelope to `https://api.hanzo.ai/v1/mcp`.

```bash
curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "billing",
         "arguments": {
           "op": "get_billing_crypto_gateway_by_id",
           "input": {
             "id": "<id>"
           }
         }
       }
     }'
```

---

[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)