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.

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.

This field should contain the payment amount for the transaction.

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

The first name of the customer.

The email address of the customer.

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.

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.

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)

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

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

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

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

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.

User-defined fields (udf) are used to store any information corresponding to a particular transaction. You can use up to five udfs in the post designated as udf1, udf2, udf3, udf4, udf5.

User-defined fields (udf) are used to store any information corresponding to a particular transaction. You can use up to five udfs in the post designated as udf1, udf2, udf3, udf4, udf5.

User-defined fields (udf) are used to store any information corresponding to a particular transaction. You can use up to five udfs in the post designated as udf1, udf2, udf3, udf4, udf5.

User-defined fields (udf) are used to store any information corresponding to a particular transaction. You can use up to five udfs in the post designated as udf1, udf2, udf3, udf4, udf5.

User-defined fields (udf) are used to store any information corresponding to a particular transaction. You can use up to five udfs in the post designated as udf1, udf2, udf3, udf4, udf5.

This parameter must have the source IP of the customer.

This parameter must have the customer agent's device.