Here are two request examples for the Generate RSA signature REST API operation.

Example 1: One-time UPI Intent payment with amount and currency

Use this pattern when you want to charge a customer immediately with a one-time UPI Intent payment. Include both the payment amount and the transaction currency in the signed payload.

Send a request similar to the following for the Generate RSA signature REST API operation:

{
  "uri": "https://sandbox.na.zuora.com/apps/PublicHostedPageLite.do",
  "method": "POST",
  "pageId": "<YOUR_PAYMENT_PAGE_ID>",
  "paymentGateway": "<YOUR_ADYEN_V2_GATEWAY>",
  "authorizationAmount": "100",
  "currency": "INR",
  "accountId": "<YOUR_ACCOUNT_ID>"
}

For one-time UPI Intent payments, include at least the following fields in the signed payload:

• authorizationAmount: The one-time payment amount.

• currency: The transaction currency. For UPI on Adyen Integration v2.0, this must be INR.

Example 2: UPI Autopay or validation without an immediate charge

Use this pattern when you want to create or validate a UPI payment method or mandate without charging the customer immediately, for example as part of a UPI Autopay setup flow.

You can omit the authorizationAmount and currency fields from the signature request when you are not collecting a one-time payment during the Payment Page session.

The following example shows a minimal request body for the Generate RSA signature REST API operation in this scenario:

{
  "uri": "https://sandbox.na.zuora.com/apps/PublicHostedPageLite.do",
  "method": "POST",
  "pageId": "<YOUR_PAYMENT_PAGE_ID>",
  "paymentGateway": "<YOUR_ADYEN_V2_GATEWAY>",
  "accountId": "<YOUR_ACCOUNT_ID>"
}

When you use this pattern:

• The Payment Page session can be used to collect and tokenize UPI details for later use in UPI Autopay flows.

• The actual recurring debits are initiated later by Zuora by using the stored mandate and token information, according to your billing and payment run configuration.