CB - UPI

post

https://test.payu.in/_payment

Merchant-hosted UPI payment for Cross-Border integrations. Collect the customer VPA on your site and post to /_payment.

PayU allows you to collect payments using UPI handles. For the list of UPI providers supported, refer to UPI Handles. The buyer_type_business parameter is used for Cross Border payment transactions to indicate the type of business of the buyer.

After the payment is complete, you must use the Invoice Upload API to upload invoices / AWBs (Air-way bill number). AWB details are mandatory for Goods transactions.

Important Recommendations

📘
Notes:

NPCI recommends avoiding execution during peak hours, specifically between 10:00 AM to 1:00 PM and 5:00 PM to 9:30 PM. This measure aims to enhance the user experience for UPI Autopay.=> All other transactions will continue to function seamlessly as they currently do.

Merchants are requested to refrain from initiating UPI Autopay executions during these peak hours to avoid failures due to these restrictions.

Above execution timing and limiting the execution attempts to 4 will be applicable post 31st July, 2026.

Combination of debit Frequency as "ADHOC" (As on when presented) and category as "Loan EMI payment " is not allowed as per NPCI guidelines for ENACH bank mandates and Loan merchants are restricted to create the bank mandates on other frequencies such as MONTHLY.

📘
Reference: For steps to integrate UPI for Cross-Border Payments, refer to [S2S] UPI Consent Transaction - Cross Border

Recommended prerequisite before initiating payment

When your customer makes payment through UPI, you can validate the customer's Virtual Payment Address (VPA) and then initiate payment. The validateVpa API is used to validate the UPI handle.

Validate the VPA (UPI handle) using the validateVpa API. For more information, refer to Validate VPA Handle API.

Environment

Environment	URL
Test Environment	https://test.payu.in/_payment
Production Environment	https://secure.payu.in/_payment

Sample request

  curl --location --request POST 'https://test.payu.in/_payment' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'key=JPM7Fg' \
  --data-urlencode 'txnid=payuTestTransaction12345' \
  --data-urlencode 'amount=100.00' \
  --data-urlencode 'firstname=Ashish' \
  --data-urlencode '[email protected]' \
  --data-urlencode 'phone=9988776655' \
  --data-urlencode 'productinfo=Product Info' \
  --data-urlencode 'surl=https://test.payu.in/admin/test_response' \
  --data-urlencode 'furl=https://test.payu.in/admin/test_response' \
  --data-urlencode 'pg=UPI' \
  --data-urlencode 'bankcode=INTENT' \
  --data-urlencode 'txn_s2s_flow=4' \
  --data-urlencode 's2s_client_ip=10.200.12.12' \
  --data-urlencode 's2s_device_info=Mozilla/5.0 (Windows NT 10.0; Win64; x64) PayU-API-Test/1.0' \
  --data-urlencode 'udf1=AELPR1234E' \
  --data-urlencode 'udf3=02-02-1980' \
  --data-urlencode 'udf4=XYZ Pvt. Ltd.' \
  --data-urlencode 'udf5=INV123456' \
  --data-urlencode 'buyer_type_business=1' \
  --data-urlencode 'udf_params={"udf7":"0100000029","udf8":"99953729071"}' \
  --data-urlencode 'hash=YOUR_CALCULATED_HASH'

Sample Response

Collect the response in the UPI Collection - S2S. under API Reference. For description of response parameters, refer to Additional Info for Payment APIs.

Using the IntentURIData value in response

The IntentURIData parameter returns the URI in the response. For example, it contains the first debit amount .

📘
Notes:

Every time there is a change, you need to incorporate the changes to avoid breaking the transactions.

The tid value which is passed in the intent URI acts as a validation check at NPCI's end which do not allow duplicate transaction.

The tr value not necessary and it is a payU_id. It can be any reference id for PayU's internal reconciliation.

Parsed response

{ 
  "rawBankData" : ""  
  "referenceId":  "00c44a4c8306f9cbe5ecf6133afe08a7" 
  "bankData" : { 
  "referenceId": "00c44a4c8306f9cbe5ecf6133afe08a7", 
  "messageDigest": "c2e9e456037f033e5cc3d7b6e556189adf41eeabf706844dff70aac91f6b8e73bb1846286c8f99ea768cf38f7c12369c|523727493647950f32684bd6f1ab07aa6474016f", 
  "pares": "eNrVmdeS47i2pl+lo8+loje968jOCHojGtGLvKM3opHoyacfZmZVde06PWfOzMXEjCIUgkBiYRHAWv8H4s0phyzj7CyZh+z9TcvGMSqy36r0r99jFAfhGIT/gLE8/QNNM/IPEiGoP5CUgGEwAjGCSH9/f7vRVjZ+NvgsnTVLNoxV371D/wL/Bb8B3/+exoekjLrp/S1KXoysv6MkQhHYG/Dt71ubDTL3DkMwhZIgRoIIAoL4G/BV/Qb83f42f5TG0+GtSt9Dp5gMTkMMGzxCLtm1mik1zkV02PzrDfi44y2NpuwdBuHTNgj9BiF/IsSfyOnbZ/3b88Mc3fbzaRuCwDfg54q3c2SGrEv2dwQ7nfnx7y3bnn2XnXecdn6U34C/fXtG3Tv40wcFQeK0fda+Off3t6lqf/YJ/RMi/4ShN+Cz/m2comme34M34FvpLYmW5Z2maYYVTJqWzadhJqu+0t8/57N+3vKWJdU7eA7rx+9nK7op+qGayvbD1X+veAM+XAE+p+79za6K7uxsyH7b2qYb//q9nKbnnwCwruu/VuRf/VAA8PkgAEgB5w3pWBX/8ftXqyyVu7z/32rGRl3fVUnUVEc0nQtEy6ayT3/74ds/mXGsD0sQYPHsH6epPxII7f74qAERCDttAv9s9Kcn++/08quzwxj9MZYR9NHBL4be36wszz5WRPaba8l//f4f36OAq4psnP5Puvve1c8WvtvzombO3mc3DXRwZEp92R+80+1LH1P8RNQ4/9f3dl93vgE//Pvm/NdM/TQiXzc6RMf6GG04qXdxrxgV1PAQ4FJa38tkuNT", 
  "additionalInfo": 
  { 
      "authUdf1": "", 
      "authUdf2": "", 
      "authUdf3": "", 
      "authUdf4": "", 
      "authUdf5": "", 
      "authUdf6": "", 
      "authUdf7": "", 
      "authUdf8": "", 
      "authUdf9": "", 
      "authUdf10": "" 
  } 
}, 
  "authenticationStatus"  :  "success", 
  "hash" : "664b8ddd1b5b2d1b68abb7eee5ea6e001a02773499ddcd86956ba0833315e7d4e69c641d7b0b3e7590532e21e71936da173f4eda716fc09f83cd1117f0d0c37c"}

Request parameters

Additional info for request parameters

Payment Request Parameters

The payment request parameters include standard fields like key, txnid, amount, firstname, email, phone, and productinfo. For UPI payments, the following specific parameters are important:

pg: Set to "UPI" to indicate UPI payment method
bankcode: Set to "UPI" for UPI transactions
vpa: The Virtual Payment Address (UPI ID) of the customer

For a comprehensive list of all parameters and their descriptions, refer to the following:

📘
Reference: For the character limit of each parameter and detailed description, refer to Additional Info for Payment APIs.

🚧
Testing UPI: You can test UPI only with the anything@payu or [email protected] as VPA.

❗️
Error handling: If any error message is displayed with an error code, refer to the Error Codes section to understand the reason for these error codes.

Form Data

Form-encoded payment request for Cross-Border UPI.

key

string

required

Merchant key provided by PayU during onboarding.

txnid

string

required

The transaction ID is a reference number for a specific order that is generated by the merchant.

amount

string

required

The payment amount for the transaction. Post as a decimal string (for example, "10" or "10.00").

productinfo

string

required

A brief description of the product.

firstname

string

required

The first name of the customer.

surl

uri

required

The success URL, which is the page PayU will redirect to if the transaction is successful.

furl

uri

required

The failure URL, which is the page PayU will redirect to if the transaction fails.

string

required

The email address of the customer.

string

required

The pg parameter determines which payment tab is used. For UPI, use UPI.

bankcode

string

required

Each payment option is identified with a unique bank code at PayU. For UPI, post UPI.

vpa

string

required

The customer UPI handle (VPA) provided by the bank for UPI payments.

hash

string

required

Hash calculated by the merchant. Format: sha512(key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3|udf4|udf5||||||SALT)

phone

string

The phone number of the customer.

lastname

string

The last name of the customer.

buyer_type_business

string

Identifies a B2B transaction. Post 1 for B2B.

curl

uri

The cancel URL, which is the page PayU will redirect to if the transaction is cancelled by the customer.

udf1

string

Buyer PAN (Permanent Account Number). For UPI mandate or recurring, use Buyer's PAN||Buyer's DOB (separated by two pipe characters).

udf2

string

User-defined field for transaction metadata (udf2).

udf3

string

This parameter is optional but recommended for a higher approval rate. Date of birth (DOB) of the buyer in DD-MM-YYYY format.

udf4

string

Merchant name for PA2PA integrations. Do not pass for UPI mandate or recurring transactions.

udf5

string

Invoice ID for the merchant. Mandatory during or after the transaction (including via the udf_update API post successful transaction).

Headers

string

enum

Defaults to text/plain

Generated from available response content types

Allowed:

Responses

302

Redirect to UPI app, bank, or merchant surl / furl (typical flow).

Language

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

text/plain

text/html

Notes:

Recommended prerequisite before initiating payment

Environment

Notes:

Request parameters

Payment Request Parameters

200May return HTML or a query-string style body (for example, mihpayid=…&status=success&…) depending on integration. Verify hash on return using PayU post-response hash rules.

EXAMPLE QUESTIONS