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

# PayU

Configure PayU card and wallet payments with Hyperswitch.

<div align="left"><img src="https://hyperswitch.io/icons/homePageIcons/logos/payuLogo.svg" alt=""></div>

PayU places Apple Pay and Google Pay beside credit and debit cards in its payment gateway integration. Each route uses automatic, manual, or sequential automatic capture, and refunds are supported. Mandates are not supported.

### Status and capabilities

**Integration status:** sandbox

**Category:** payment gateway

**Webhook flows:** None declared in code

| Payment method | Type        | Mandates      | Refunds   | Capture methods                         | 3DS            | Card networks                                                                                       | Countries                                         | Currencies                                        |
| -------------- | ----------- | ------------- | --------- | --------------------------------------- | -------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------- |
| card           | Credit Card | not supported | supported | automatic, manual, sequential automatic | required       | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Mastercard, UnionPay, Visa | 134 ([full list](https://hyperswitch.io/pm-list)) | 134 ([full list](https://hyperswitch.io/pm-list)) |
| card           | Debit Card  | not supported | supported | automatic, manual, sequential automatic | required       | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Mastercard, UnionPay, Visa | 134 ([full list](https://hyperswitch.io/pm-list)) | 134 ([full list](https://hyperswitch.io/pm-list)) |
| wallet         | Apple Pay   | not supported | supported | automatic, manual, sequential automatic | not applicable | -                                                                                                   | -                                                 | -                                                 |
| wallet         | Google Pay  | not supported | supported | automatic, manual, sequential automatic | not applicable | -                                                                                                   | 46 ([full list](https://hyperswitch.io/pm-list))  | 53 ([full list](https://hyperswitch.io/pm-list))  |

### Activate PayU with Hyperswitch

#### Before you start

1. You need to be registered with PayU. Sign up at [corporate.payu.com](https://corporate.payu.com/).
2. Sign in to the [Hyperswitch control center](https://app.hyperswitch.io/) or create your Hyperswitch account.
3. In the PayU dashboard, open **My Shops** and copy your API Key and Merchant POS ID.
4. Enable the same payment methods in PayU and in your Hyperswitch connector configuration.

To connect PayU to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for what PayU supports.

### Connector-Specific Notes

PayU obtains an access token with a form-encoded client credentials request before it sends transaction requests. Hyperswitch manages this exchange, so configure the connector credentials rather than supplying an access token directly. See [`PayuAuthUpdateRequest`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/payu/transformers.rs#L323-L336).

### Authentication

Provide an **API key** and **merchant POS ID**. The `BodyKey` auth mapping assigns `api_key` to the API key and `key1` to the merchant POS ID; the token request sends the merchant POS ID as `client_id` and the API key as `client_secret`. See [`PayuAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/payu/transformers.rs#L188-L203) and [`PayuAuthUpdateRequest::try_from()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/payu/transformers.rs#L323-L336).

Transaction requests use `Authorization: Bearer <access token>`. The connector's common auth path can also return `Authorization: <API key>`, while the transaction header builder requires the exchanged token. See [`build_headers()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/payu.rs#L70-L96) and [`get_auth_header()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/payu.rs#L112-L123).

### Webhooks

Webhooks are not currently supported. Payment status updates rely on syncing with the API. The webhook implementation returns `EventNotSupported` and does not provide a resource object. See [`get_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/payu.rs#L785-L808).

### Source reference

The connector implementation is [`payu.rs`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/payu.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.