PayU Hosted Checkout with Pre-Authorize Payment

key

const

enum

required

This parameter must contain the merchant key that was provided by PayU while onboarding.

Allowed:

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

integer

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.

email

string

required

The email address of the customer.

phone

number

required

The phone number of the customer.

pre_authorize

const

enum

required

This field must contain value as 1 to pre-authorize payments.

Allowed:

surl

const

enum

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.

Allowed:

furl

const

enum

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.

Allowed:

hash

string

required

This parameter must contain the hash value to be calculated at merchant end.

enforce_paymethod

const

enum

required

This parameter must contain the hash value to be calculated at merchant end.

Allowed:

lastname

string

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

curl

string

The "curl" field is the Cancel URL, which is the page PayU will redirect to if the transaction is canceled by the customer. The merchant can handle the response at this URL after the customer is redirected there.

udf1

string

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.

udf2

string

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.

udf3

string

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.

udf4

string

udf5

string

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.

200

EXAMPLE QUESTIONS