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

# IATA Pay

Configure IATA Pay bank redirect, real-time payment, and UPI payments with Hyperswitch.

IATA Pay connects bank redirect, real-time payment, and UPI routes to Hyperswitch. Every declared route supports refunds with automatic capture. Payment and refund callbacks are verified before status updates are applied.

### Status and capabilities

**Integration status:** live

**Category:** payment gateway

**Webhook flows:** payments, refunds

| Payment method    | Type                | Mandates      | Refunds   | Capture methods | Countries | Currencies |
| ----------------- | ------------------- | ------------- | --------- | --------------- | --------- | ---------- |
| bank redirect     | iDEAL               | not supported | supported | automatic       | NLD       | EUR        |
| bank redirect     | Local Bank Redirect | not supported | supported | automatic       | 28        | 15         |
| real time payment | DuitNow             | not supported | supported | automatic       | MYS       | MYR        |
| real time payment | FPS                 | not supported | supported | automatic       | GBR       | GBP        |
| real time payment | PromptPay           | not supported | supported | automatic       | THA       | THB        |
| real time payment | VietQR              | not supported | supported | automatic       | VNM       | VND        |
| upi               | UPI Collect         | not supported | supported | automatic       | IND       | INR        |
| upi               | UPI Intent          | not supported | supported | automatic       | IND       | INR        |

### Authentication

Provide **Client ID**, **Airline ID**, **Client Secret**, and **Source verification key** from [`iatapay connector configuration`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/connector_configs/toml/sandbox.toml#L3072-L3077); [`IatapayAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/iatapay/transformers.rs#L259-L275) maps the API credentials.

### Before you start

Create or sign in to your [IATA Pay account](https://www.iata.org/en/services/finance/iata-pay/) and obtain the **Client ID**, **Airline ID**, **Client Secret** and the webhook signing secret you will enter as **Source verification key**. IATA Pay appears in the control center list ([`connectorList`](https://github.com/juspay/hyperswitch-control-center/blob/ecca16a27cb6acb336569ea30714fa05d867c765/src/screens/Connectors/ConnectorUtils.res#L89-L205)). Then follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md).

### Webhooks

IATA Pay verifies callbacks with HMAC-SHA256 over the raw body. The Base64 signature follows the `IATAPAY-HMAC-SHA256` prefix in the `Authorization` header ([`IATA Pay webhook verification`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/iatapay.rs#L670-L699)).

The payment enum defines nine known wire values and the refund enum seven ([`IATA Pay webhook event mapping`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/iatapay/transformers.rs#L659-L718)).

| Payload | Wire value           | Effect                        |
| ------- | -------------------- | ----------------------------- |
| Payment | `AUTHORIZED`         | Payment succeeds              |
| Payment | `SETTLED`            | Payment succeeds              |
| Payment | `INITIATED`          | Payment remains in processing |
| Payment | `FAILED`             | Payment fails                 |
| Payment | `CREATED`            | No payment update             |
| Payment | `CLEARED`            | No payment update             |
| Payment | `TOBEINVESTIGATED`   | No payment update             |
| Payment | `BLOCKED`            | No payment update             |
| Payment | `UNEXPECTED SETTLED` | No payment update             |
| Refund  | `CLEARED`            | Refund succeeds               |
| Refund  | `AUTHORIZED`         | Refund succeeds               |
| Refund  | `SETTLED`            | Refund succeeds               |
| Refund  | `FAILED`             | Refund fails                  |
| Refund  | `CREATED`            | No refund update              |
| Refund  | `LOCKED`             | No refund update              |
| Refund  | `INITIATED`          | No refund update              |

### Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch `7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8`. See [IATA Pay connector source](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/iatapay.rs) and [IATA Pay transformers](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/iatapay/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/iatapay.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.