PayU Hosted Integration

The pre_authorize parameter is used to pre-authorize payments using the PayU Hosted Checkout integration with the _payment API.

📘

Note:

You need to activate the Pre-Authorize Payments before you start using this integration. Contact your PayU Key Account Manager (KAM) to activate Pre-Authorize Payments.

Step 1: Post the pre-auth transaction request

Post the additional parameters for using the Pre-Auth. For complete list of parameters, refer to Pre-Authorize Payment for the complete list parameters with Try It experience.

Environment

The pre_authorize parameter as specified is used to pre-authorize payments using the PayU Hosted Checkout integration with the _payment API.

Parameter

Description

Example

key mandatory

StringMerchant key provided by PayU during onboarding.

JPG****.k

txnid
mandatory

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

ypl938459435

amount
mandatory

StringThe payment amount for the transaction.

10.00

productinfo
mandatory

StringA brief description of the product.

iPhone

firstname
mandatory

String The first name of the customer.

Ashish

email
mandatory

StringThe email address of the customer.

[email protected]

phone
mandatory

StringThe phone number of the customer.

lastname
optional

String The last name of the customer.

Kumar

surl
mandatory

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

https://test-payment-middleware.payu.in/simulatorResponse

furl
mandatory

String The Failure URL, which is the page PayU will redirect to if the transaction is failed.

https://test-payment-middleware.payu.in/simulatorResponse

pre_authorize
mandatory for Pre-Auth

String This parameter is set to1 to pre-authorize payment using PayU Hosted Checkout.

hash
mandatory

String It is the hash calculated by the merchant.

  • Reference*: For detailed information on hashing, refer to Generate Hash .

address1
optional

String The first line of the billing address.

  • Fraud Detection*: This information is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information.

H.No- 17, Block C, Kalyan Bldg, Khardilkar Road, Mumbai

address2
optional

String The second line of the billing address.

34 Saikripa-Estate, Tilak Nagar

city
optional

String The city where your customer resides as part of the billing address.

Mumbai

state
optional

String The state where your customer resides as part of the billing address,

Maharashtra

country
optional

String The country where your customer resides.

India

zipcode
optional

String Billing address zip code is mandatory for the cardless EMI option.
Character Limit-20

400004

enforced_payment
optional

StringThis parameter is to customize the payment options for each transaction. You can enforce specific payment modes, cards scheme, and specific banks under Net Banking using this method.

creditcard|debitcard

drop_category
optional

StringThis parameter is used if you want to hide one or multiple payment options. For example, if you consider the payment options such as credit card, debit card, and net banking, you can hide the credit card mode of payment.

CC

udf1
optional

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.

AELPR****E

udf2
optional

StringUser-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
optional

String User-defined fields (udf) are used to store any information corresponding to a particular transaction.

02-02-1980

udf4
optional

StringUser-defined fields (udf) are used to store any information corresponding to a particular transaction.

XYZ Pvt. Ltd.

udf5
optional

StringUser-defined fields (udf) are used to store any information corresponding to a particular transaction.

098450845

Hashing

You must hash the request parameters using the following hash logic:

sha512(key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3|udf4|udf5||||||SALT)

For more information, refer to Generate Hash.

Sample request

curl -X POST "https://test.payu.in/_payment
-H "accept: application/json" -H "Content-Type: application/x-www-form-urlencoded" -d
"key=JP***g&txnid=PQI6MqpYrjEefU&amount=10.00
&firstname=PayU User&[email protected]&phone=9876543210
&productinfo=iPhone&pre_authorize=1&pg=cc&bankcode=CC&surl=
https://apiplayground-response.herokuapp.com/
&furl=https://apiplayground-response.herokuapp.com/
&pre_authorize=1&hash=05a397501918ec5c36ae52daa3b3e49b43e986b86940e109d060076e467c3ea7536617df7420e0e6863dced8c5b45f9fff15c13bdf0335512c05f0210b31b072"

Step 2: Check the response from PayU

Hash validation logic for payment response (Reverse Hashing)

While sending the response, PayU takes the exact same parameters that were sent in the request (in reverse order) to calculate the hash and returns it to you. You must verify the hash and then mark a transaction as a success or failure. This is to make sure the transaction has not tampered within the response.

The order of the parameters is similar to the following code block:

sha512(SALT|status||||||udf5|udf4|udf3|udf2|udf1|email|firstname|productinfo|amount|txnid|key)

Sample response

By default, the response in HTML format. The formatted sample response body is similar to the following, and you need to look for the following parameters:

  • PG_TYPE: CC PG
  • bankcode: CC
  • unamappedstatus: auth
mihpayid: 403993715523615328
mode: CC
status: success
unmappedstatus: auth
key: JPM7Fg
txnid: 50QJq6lBJBmx14
amount: 10.00
cardCategory: domestic
discount: 0.00
net_amount_debit: 10
addedon: 2021-07-28 15:11:37
productinfo: iPhone
firstname: PayU User
lastname: 
address1: 
address2: 
city: 
state: 
country: 
zipcode: 
email: [email protected]
phone: 9876543210
udf1: 
udf2: 
udf3: 
udf4: 
udf5: 
udf6: 
udf7: 
udf8: 
udf9: 
udf10: 
hash: afeab9dcf4e43d47f8fbf5a6838d393c70694a58e30ada08e6cb86ac943236c05717c5f5e4872d671fe81d0d9b2d9facd44e9a061ba621aff6f20c4343ea5dfa
field1: 
field2: 
field3: 
field4: 
field5: 
field6: 
field7: 
field8: 
field9: Transaction Completed Successfully
payment_source: payu
PG_TYPE: CC-PG
bank_ref_num: 7f0d5ada-59bb-41d7-9e41-20a6af2406c9
bankcode: CC
error: E000
error_Message: No Error
name_on_card: test
cardnum: 411111XXXXXX1111
cardhash: This field is no longer supported in postback params.

Step 3: Capture a Pre-authorized payment

To capture a pre-authorized payment, use the following command. After the API command is successful, the transaction would be captured and settled to you.

Environment

Sample request

curl --location --request POST 'https://info.payu.in/merchant/postservice.php?form=2' \ 
--header 'Content-Type: application/x-www-form-urlencoded' \ 
--form 'key="JF***g"' \ 
--form 'command="capture_transaction"' \ 
--form 'hash="67411736ab98c59522492a12751a6015c41b87764019f9dc14052690c2c7af9095d31002fc109dcf3596c2f38792d56db6f6207b1989010f2adf51c144fa3019"' \ 
--form 'var1="15246574846"' \ 
--form 'var2="authorizeTransaction123"' \ 
--form 'var3="1"' 

Sample response

{ 
    "status": 1, 
    "msg": "Capture Request Queued", 
    "request_id": "Request ID", 
    "bank_ref_num": "Bank Reference Number" 
} 

Step 3: Check Action Status

  • To check the status of the transaction, use the verify_payment API. For more information, refer to Verify Payment API
  • To check the status of the Auth Request and then Capture Request sent, use the check_action_status API. For more information, refer to Check Refund Status API with Request ID.

📘

Note:

Sample response

Failure scenario

{ 

    "status": 1, 

    "msg": "1 out of 1 Transactions Fetched Successfully", 

    "transaction_details": { 

        "18315176038": { 

            "12806028149": { 

                "mihpayid": "18315176038", 

                "bank_ref_num": "6969235068376733806127", 

                "request_id": "12806028149", 

                "amt": "2.00", 

                "mode": "CC", 

                "action": "auth", 

                "token": "", 

                "status": "SUCCESS", // Auth is successful 

                "bank_arn": null, 

                "settlement_id": null, 

                "amount_settled": null, 

                "UTR_no": null, 

                "value_date": null, 

                "refund_mode": "-" 

            }, 

            "12806028151": { 

                "mihpayid": "18315176038", 

                "bank_ref_num": null, 

                "request_id": "12806028151", 

                "amt": "1.00", 

                "mode": "CC", 

                "action": "capture", 

                "token": "Cap_18315176038_01", 

                "status": "QUEUED", // Capture is in queue statue  

                "bank_arn": null, 

                "settlement_id": null, 

                "amount_settled": null, 

                "UTR_no": null, 

                "value_date": null, 

                "refund_mode": "-" 

            } 

        } 

    } 

Success scenario

{ 
    "status": 1, 
    "msg": "1 out of 1 Transactions Fetched Successfully", 
    "transaction_details": { 
        "18283829909": { 
            "12781896792": { 
                "mihpayid": "18283829909", 
                "bank_ref_num": "6966342376826003206121", 
                "request_id": "12781896792", 
                "amt": "1031.00", 
                "mode": "CC", 
                "action": "auth", 
                "token": "", 
                "status": "SUCCESS", 
                "bank_arn": null, 
                "settlement_id": null, 
                "amount_settled": null, 
                "UTR_no": null, 
                "value_date": null, 
                "refund_mode": "-" 
            }, 
            "12781896793": { 
                "mihpayid": "18283829909", 
                "bank_ref_num": "6969233152136917105030", 
                "request_id": "12781896793", 
                "amt": "426.00", 
                "mode": "CC", 
                "action": "capture", 
                "token": "PZT2310070446VG2VC01", 
                "status": "success", // Auth is successful 
                "bank_arn": null, 
                "settlement_id": "202310111115", 
                "amount_settled": "418.7100", 
                "UTR_no": null, 
                "value_date": null, 
                "refund_mode": "-" 
            }, 
            "12806008126": { 
                "mihpayid": "18283829909", 
                "bank_ref_num": null, 
                "request_id": "12806008126", 
                "amt": "605.00", 
                "mode": "CC", 
                "action": "cancel", 
                "token": "825816e28afb809be802c7b", 
                "status": "SUCCESS", // Capture is successful 
                "bank_arn": null, 
                "settlement_id": null, 
                "amount_settled": null, 
                "UTR_no": null, 
                "value_date": null, 
                "refund_mode": "-" 
            } 
        } 
    } 

}