Cards Direct Authorization Flow

PayU enables merchants to process direct authorization for pre-authenticated transactions (external MPI/3DSS). This section describes how to integrate with PayU’s direct authorization flow. Initiate an authorization request with the payment details provided post a successful authentication through the MPI/3DSS as explained in this API Reference. You can get the sample request and response when use the "Try It" experience. For more information remaining steps of integration, refer to Direct Authorization Integration.

📘
Note:
This API is backward compatible and you can continue to the existing integration parameters to process the 3DS 1.0.2 transactions.

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: Access Production Key and Salt Test: Access 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*: Hash logic for _payment API version 19: The following hash logic must be used for _payment API withapi_version=19: `key\\|txnid\\|amount\\|productinfo\\|firstname\\|email\\|udf1\\|udf2\\|udf3\\|udf4\\|udf5\\|udf6\\|udf7\\|udf8\\|udf9\\|udf10\\|user_token\\|offer_key\\|offer_auto_apply\\|cart_details\\|extra_charges\\|phone`

Parameter

Reference

key

For more information on how to generate the Key and Salt, refer to any of the following:

Production: Access Production Key and Salt
Test: Access 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*: Hash logic for _payment API version 19:

The following hash logic must be used for _payment API withapi_version=19:
key\|txnid\|amount\|productinfo\|firstname\|email\|udf1\|udf2\|udf3\|udf4\|udf5\|udf6\|udf7\|udf8\|udf9\|udf10\|user_token\|offer_key\|offer_auto_apply\|cart_details\|extra_charges\|phone

📘
Note: The following request parameters are mandatory for Cross-Border Payments in addition to user-defined parameters specified above: firstname, lastname, address1, city, state, country and zipcode.

📘
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

Collect info for Fraud Detection & Chargeback Prevention

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
If any error message is displayed with an error code, refer to the Error Codes section to understand the reason for these error codes. Also, for error codes during various transaction stages in Net Banking, Cards and Wallets, refer to Transaction Stages - Transaction Stages - Error References on Field7 & Field8.

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