Prepare your environment for Adyen UPI QR integration
Learn how to enable and configure UPI for Adyen Integration v2.0, including tenant-level activation, gateway configuration, and required reconciliation setup for UPI QR on desktop.
To configure an Adyen gateway instance for processing UPI (including UPI QR) transactions, follow Set up and configure an Adyen Integration v2.0 gateway instance and then apply these UPI-specific notes:
- UPI does not support Additional Metadata, so you can ignore / skip any Additional Metadata settings for this gateway instance when you are configuring UPI-only flows.
-
Settings with fixed values for UPI on Adyen.
-
Before testing UPI QR with Adyen, contact Adyen to enable the
UPI Payment Method Indiasimulator with the acquirer accountHDFCIndiaRecurringSimulatorAcquirerAccountfor your test environment. This is a mandatory prerequisite for testing. After the simulator is enabled, use the Adyen test magic numbers to validate the supported scenarios.
The following values are fixed by the integration for UPI and cannot be overridden via gateway configuration:
| Setting | Value passed to Adyen (UPI) |
|---|---|
| Country / currency | UPI on Adyen Integration v2.0 only supports IN / INR for UPI transactions. |
| shopperInteraction | Ecommerce for one-time payments, ContAuth for recurring payments. |
| recurringProcessingModel | Subscription. To override, use param_gwOptions_recurringProcessingModel in the Payment Pages 2.0 request. |
Enablement of zero-amount validation (optional)
- Zero-amount validation for UPI on Adyen is not enabled by default.
- To use zero-amount validation , you only need to set the default amount on the gateway instance and send
gwOptions_additionalAmountthrough HPM. No additional gateway configuration is required for this step.
UPI Autopay mandate configuration for Adyen UPI QR
Use the following gateway options to configure UPI Autopay mandates for Adyen Integration v2.0 when you invoke Payment Pages 2.0, Payment Form, or the API for UPI QR flows.
| Option | Description | Example | Default |
|---|---|---|---|
gwOptions_UpiQrMandateEnabled | Enables UPI mandate creation for Autopay when processing UPI QR payments. | true | N/A |
gwOptions_UpiMandateAmount | Maximum mandate amount for UPI Autopay. This value is required when Autopay is enabled. | 100000 | N/A |
gwOptions_UpiMandateStartsAt | Mandate start date in YYYY-MM-DD format. | 2025-07-21 | N/A |
gwOptions_UpiMandateEndsAt | Mandate end date in YYYY-MM-DD format. | 2030-07-21 | N/A |
gwOptions_UpiMandateRemarks | Free-form description or remark for the mandate. | MandateRemark | Empty |
gwOptions_UpiMandateAmountRule | Amount rule for the mandate. Valid values are max (up to the maximum amount) and exact (fixed amount). | max | max |
gwOptions_UpiMandateFrequency | Billing frequency for Autopay. Valid values are adhoc, daily, weekly, and monthly. | monthly | adhoc |
gwOptions_UpiMandateBillingDay | Billing day of the month (1–31) when gwOptions_UpiMandateFrequency is set to monthly. | 25 | 1 |
gwOptions_UpiMandateBillingAttemptsRule | Rule that determines whether billing attempts occur before or after the scheduled billing day. Valid values are before and after. | before | after |
gwOptions_additionalAmount | Use this option to pass the additional amount through HPM. | 200 | N/A |