> 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/hyperpg.md).

# HyperPG

Configure HyperPG card payments with Hyperswitch.

HyperPG processes credit and debit card payments through Hyperswitch, with automatic capture, refunds and optional 3DS. Mandates are not supported. HyperPG is not offered in the Hyperswitch control center, so you set it up through the API.

To connect HyperPG to your Hyperswitch account, create the connector account as described under Before you start, then return here for what HyperPG supports and how a payment moves.

### Status and capabilities

**Integration status:** live

**Category:** payment gateway

**Webhook flows:** None declared in code

| Payment method | Type        | Mandates  | Refunds   | Capture methods | 3DS                 | Card networks                                                                                                | Countries | Currencies         |
| -------------- | ----------- | --------- | --------- | --------------- | ------------------- | ------------------------------------------------------------------------------------------------------------ | --------- | ------------------ |
| card           | Credit Card | supported | supported | automatic       | supported, optional | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Maestro, Mastercard, UnionPay, Visa | -         | EUR, GBP, INR, USD |
| card           | Debit Card  | supported | supported | automatic       | supported, optional | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Maestro, Mastercard, UnionPay, Visa | -         | EUR, GBP, INR, USD |

HyperPG runs through the Unified Connector Service ([`ucs_only_connectors`](https://github.com/juspay/hyperswitch/blob/01365da86035c7bb6ebe99126443248d811cbcaf/config/deployments/production.toml#L1099)).

The table reflects the declaration ([`HYPERPG_SUPPORTED_PAYMENT_METHODS`](https://github.com/juspay/hyperswitch/blob/01365da86035c7bb6ebe99126443248d811cbcaf/crates/hyperswitch_connectors/src/connectors/hyperpg.rs#L588-L655)). The service implements authorize, payment sync, refund and refund sync ([flows](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L106-L175)). Capture, void, mandate setup and repeat payments are not implemented ([flow status](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L466-L495)), so every payment is captured automatically and cannot be cancelled through Hyperswitch.

The table marks mandates as supported, but the service cannot set one up, run a repeat payment, or return a mandate reference ([flow status](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L466-L495), [`mandate_reference`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg/transformers.rs#L408)). Treat mandates and recurring payments as not supported through HyperPG.

### Authentication

HyperPG needs three values: a username, a password and a merchant id. The connector form only defines **Username** and **Password** ([`[hyperpg.connector_auth.BodyKey]`](https://github.com/juspay/hyperswitch/blob/01365da86035c7bb6ebe99126443248d811cbcaf/crates/connector_configs/toml/sandbox.toml#L8171-L8173)), and the service rejects an account that carries no merchant id ([auth mapping](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/types-traits/domain_types/src/router_data.rs#L3577-L3589)). Create the account through the API with `auth_type` set to `SignatureKey`: `api_key` is the username, `key1` the password and `api_secret` the merchant id ([`HyperpgAuthType`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg/transformers.rs#L25-L49)).

The service sends the username as HTTP Basic authentication with an empty password, and the merchant id in the `X-Merchant-Id` header as well as in the request body ([`build_headers`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L137-L158)). The password is stored but not used by any request.

### Before you start

Create or sign in to your [HyperPG account](https://hyperpg.in/) and obtain the username, password and merchant id. HyperPG is not in the control center connector list ([`connectorList`](https://github.com/juspay/hyperswitch-control-center/blob/ecca16a27cb6acb336569ea30714fa05d867c765/src/screens/Connectors/ConnectorUtils.res#L89-L205)), so there is no activation form: create the connector account through the connector-account API with the three values above.

### Payment flow

Authorize posts the card to `/txns` ([`Authorize`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L254-L283)). When HyperPG returns an authentication link, Hyperswitch redirects the customer to it and the payment is `requires_customer_action` until they return; otherwise the response status applies directly ([redirect](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg/transformers.rs#L390-L400)). HyperPG's charged status maps to charged; new, authorizing, pending and pending-VBV to pending; failed, authorization-failed and authentication-failed to the matching failures; and cancelled to voided ([`HyperpgPaymentStatus`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg/transformers.rs#L83-L108)).

A sync reads `/orders/{order_id}` using the order id the authorize response returned ([`PSync`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L285-L314)). A refund posts to `/orders/{order_id}/refunds` ([`Refund`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L316-L362)), and refund sync maps HyperPG's pending, success and failed to the same Hyperswitch states ([`RSync`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L364-L393), [`HyperpgRefundStatus`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg/transformers.rs#L113-L126)).

### Webhooks

HyperPG webhooks are not supported. The service's webhook handler is empty ([`IncomingWebhook for Hyperpg`](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs#L80-L83)), so a callback is answered with the trait default, `WebhooksNotImplemented` ([default](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/types-traits/interfaces/src/connector_types.rs#L647-L653)). Use payment sync and refund sync for status.

### Source reference

The capability declaration and credential labels on this page are tied to Hyperswitch `01365da86035c7bb6ebe99126443248d811cbcaf`. Flow, authentication and webhook behavior is tied to the Unified Connector Service implementation at hyperswitch-prism `6a4b09bf2551defe9f8b315f206d12dcea0abe24`: see [HyperPG service source](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg.rs) and [HyperPG transformers](https://github.com/juspay/hyperswitch-prism/blob/6a4b09bf2551defe9f8b315f206d12dcea0abe24/crates/integrations/connector-integration/src/connectors/hyperpg/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/hyperpg.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.