> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# UPI via Adyen

> Set up UPI payments through Adyen in Payrails, with the intent and QR code journeys and the fields each one needs.

<picture noZoom>
  ![UPI logo](https://assets.payrails.io/img/logos/upi/logo.svg)
</picture>

<picture noZoom>
  ![Adyen logo](https://assets.payrails.io/img/logos/adyen/logo-full-bleed.svg)
</picture>

Accept [UPI](https://docs.payrails.com/docs/integrations/payment-methods/upi) payments from customers in India with Adyen as the payment service provider (PSP). The customer approves the payment in a UPI app, either through a deep link or by scanning a QR code.

## Supported workflows

<table>
  <thead>
    <tr><th>Workflow</th><th>Supported</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Before you begin

Complete these steps before you send your first UPI payment through Adyen:

1. Set up an Adyen integration in your workspace. Follow the [Adyen integration setup guide](https://docs.payrails.com/docs/integrations/payment-providers/adyen.md) if you don't have one yet.
2. Ask Adyen to enable UPI on your Adyen merchant account.
3. In the Payrails Portal, go to **Settings → Integrations**, open your Adyen integration, select **UPI** under **Payment methods**, and save.
4. Add UPI as a [payment option](https://docs.payrails.com/docs/integrations/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for Adyen

Send these fields in the authorize request, in addition to the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md). **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to the PSP when you include them.

| Field | Status | Description |
| - | - | - |
| `amount.currency` | Required | Must be `INR`. Payrails rejects other currencies. |
| `meta.paymentMethods.upi.flow` | Optional | `intent` or `qr`. Payrails rejects any other value. See [choose the journey](#choose-the-journey). |
| `paymentComposition[].paymentInstrumentData.payerFields.upiApp` | Required | Needed for the intent journey. The UPI app to open: `gpay`, `phonepe`, `paytm`, `bhim`, `cred`, `mobikwik`, `navi`, `amazonpay`, `wapay`, `jupiter`, `supermoney` or `freecharge`. |
| `meta.customer.email` | Optional | Sent to Adyen as the shopper email. |
| `meta.customer.name`, `meta.customer.lastName` | Optional | Sent to Adyen as the shopper name. |
| `meta.customer.country.code` | Optional | Sent to Adyen as the country code, for example `IN`. |
| `meta.order.softDescriptor` | Optional | Shown on the customer's bank statement. |
| `meta.order.lines` | Optional | Sent to Adyen as line items. |

## Authorize a UPI payment

### Choose the journey

Payrails picks the Adyen UPI journey from `meta.paymentMethods.upi.flow`:

* When `flow` is `intent`, the response redirects the customer to the UPI app you send in the `upiApp` payer field.
* When `flow` is `qr`, or when you don't send a `flow`, Payrails shows a QR code on a Payrails-hosted page. The customer scans it with any UPI app. Payrails ignores `upiApp` in this journey.

Call [authorize a payment](https://docs.payrails.com/reference/authorizeaction.md) with `upi` as the `paymentMethodCode`. This example uses the intent journey. The response includes the redirect to the customer's UPI app.

```json Authorize request theme={null}
{
  "amount": {
    "value": "500.00",
    "currency": "INR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "upi",
      "amount": {
        "value": "500.00",
        "currency": "INR"
      },
      "paymentInstrumentData": {
        "payerFields": {
          "upiApp": "gpay"
        }
      }
    }
  ],
  "meta": {
    "paymentMethods": {
      "upi": {
        "flow": "intent"
      }
    },
    "customer": {
      "email": "aarav.sharma@example.com",
      "name": "Aarav",
      "lastName": "Sharma",
      "country": {
        "code": "IN"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

For the QR code journey, send `"flow": "qr"` and leave out the payer fields.

The customer approves the payment in their UPI app, and Adyen sends the result to Payrails asynchronously. Confirm the result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.

## How Adyen handles UPI

* Adyen captures UPI payments automatically. When Adyen confirms the authorization, Payrails also records the capture, so the payment completes in one step.
* Payrails sends every UPI payment to Adyen as a new intent or QR code payment, never as a charge against a stored token. Each UPI payment is a new customer-initiated payment.
* The Payrails-hosted QR code page shows a five-minute countdown.
* When `flow` is `intent`, the Payrails SDK collects the UPI app through the `upiApp` payer field.
* Payrails still reads `meta.upi.flow` from older integrations. Use `meta.paymentMethods.upi.flow` for new integrations.


## Related topics

- [UPI](https://docs.payrails.com/docs/integrations/payment-methods/upi.md)
- [UPI via Unlimit](https://docs.payrails.com/docs/integrations/payment-methods/upi/unlimit.md)
- [Bancontact via Adyen](https://docs.payrails.com/docs/integrations/payment-methods/bancontact/adyen.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.