UPI Collection - S2S

post https://test.payu.in/_payment

time	status	user agent
Retrieving recent requests…

Loading…

This section provides the request and response parameters used in Step 1 of UPI Collection S2S Integration. You can get the sample request and response when use the "Try It" experience. For the complete integration steps, refer to UPI Collection S2S Integration.

Environment


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

Reference information for request parameters

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

Parameter	Reference
key	For more information on how to generate the Key and Salt, refer to any of the following: - Production: Generate Merchant Key and Salt - Test: Generate Test Merchant Key and Salt
hash	Hash logic for _payment API is: sha512(key\|txnid\|amount\|productinfo\|firstname\|email\|udf1\|udf2\|udf3\|udf4\|udf5\|\|\|\|\|\|SALT) For more information about the hash generation process, refer to Generate Hash.

📘
Note:
Collecting the information for the following parameters from customers is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information:

email

phone

address1

s2s_client_ip

s2s_device_info

Response parameters

For the response parameters, refer to Additional Info for Payment APIs.

Request parameters

🚧
Error Handling:
A list of error message with corresponding error code and reason for the error is listed in . PayU recommends you to handle these errors when you process the transactions. For more information, refer to Error Codes

🚧
Values to be used in Test environment
For values to be used in Test environment, refer to Test Cards.

Form Data

key

const

required

The merchant key is a unique identifier for a merchant account in PayU's database. It is provided by PayU and use your Test key here.

txnid

string

required

The transaction ID is a reference number for a specific order that is generated by the merchant. It is used to track the order and must be unique. PayU's system will not accept duplicate transaction IDs.

amount

string

required

This field should contain the payment amount for the transaction.

productinfo

string

required

This field should be a string containing a brief description of the product.

firstname

string

required

The first name of the customer.

string

required

The email address of the customer.

phone

number

required

The phone number of the customer.

surl

string

required

The "surl" field is the success URL, which is the page PayU will redirect to if the transaction is successful. The merchant can handle the response at this URL after the customer is redirected there.

furl

string

required

The "furl" field is the Failure URL, which is the page PayU will redirect to if the transaction is failed. The merchant can handle the response at this URL after the customer is redirected there.

hash

string

required

It is used to avoid the possibility of transaction tampering. The format for calculating the hash: sha512(key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3|udf4|udf5||||||SALT)

Please regenerate hash at the end everytime you make a change to the request parameters

notifyurl

string

It is used to send response regarding current transaction to notify about the current transaction done in merchant site.

lastname

string

Last name of the customer (must only contains alphabets).

const

required

The pg parameter determines which payment tabs will be displayed on the PayU page. UPI must be specified for UPI.

bankcode

const

required

Each payment option is identified with a unique bank code at PayU. Post UPI as bankcode for UPI.

vpa

const

required

Virtual Private Address. VPA can first be validated using VPA validate web service. Also, add regex where ‘@’ exists. This needs to be passed in case of collect flow of UPI only.

udf1

string