> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/citigate.md).

# Citigate

Connect Citigate through Hyperswitch.

Citigate appears in the Hyperswitch control center, but it is not currently usable for payment processing: its payment request conversion returns `NotImplemented`, including for cards. Do not activate Citigate for live payment traffic until the connector implements a payment method and the Hyperswitch team confirms setup.

### Status and capabilities

**Integration status:** live

**Category:** payment gateway

**Webhook flows:** None declared in code

*This connector declares no payment methods. It is a payment gateway rather than a payment processor.*

The feature matrix declares live status but no payment-method rows. The connector implementation also does not process payments, so the live label does not mean a merchant can send a payment through Citigate.

### Authentication

Citigate takes two credentials, shown in the control center as **Merchant Name** and **Merchant Password**, from [`[citigate.connector_auth.BodyKey]`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/connector_configs/toml/sandbox.toml#L9145-L9147).

[`CitigateAuthType`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/citigate/transformers.rs#L65-L85) accepts them as a `BodyKey` pair and rejects any other shape. Only the first is sent in `Authorization` by [`get_auth_header()`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/citigate.rs#L121-L132), with the remaining transport headers assembled by [`build_headers()`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/citigate.rs#L82-L95).

Citigate is a UCS-only connector: Hyperswitch forwards the credentials to the Unified Connector Service rather than calling Citigate directly, which the source notes alongside the auth type. None of this is reachable today, since no payment method is implemented.

### Before you start

1. Do not enable Citigate for payment processing; the pinned connector does not implement payment requests.
2. Contact the Hyperswitch team if you need to track the implementation or request setup.

No provider registration URL or dashboard credential path was verified for this page.

### Webhooks

Citigate does not support incoming webhooks. The object-reference, event-type, and resource handlers all return `WebhooksNotImplemented`, so there are no events or source-verification steps to configure. See [`IncomingWebhook`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/citigate.rs#L568-L587).

### Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch `ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7`. See [Citigate connector source](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/citigate.rs) and [Citigate transformers](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/citigate/transformers.rs).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/citigate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.