Resource: _payment
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: 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. |
| udf1 mandatory for Cross-Border Payments | This parameter must contain buyer’s PAN number for Cross-Border Payments. |
| udf3 mandatory for Cross-Border Payments | This parameter must contain buyer’s date of birth for Cross-Border Payments. |
| udf5 mandatory for Cross-Border Payments | This parameter must contain invoice id/awb id of the transaction for Cross-Border Payments. |
Note:
The following 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:
- 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.