You can collection payments with BNPL using Link and Pay. This section provides the request and response parameters and you can get the sample request and response when use the "Try It" experience. For more information on integration, refer to Collect Payments with BNPL using Link and Pay
Environment
| Test Environment | https://test.payu.in/_payment |
| Production Environment | https://secure.payu.in/_payment |
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. |
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
Response parameters
| Parameter | Description |
|---|---|
| metaData | JSON It is a JSON object containing more information about the response. |
| metaData.referenceId | String This is the PayU reference ID which we will be sending to merchant so that they can send us this back in second call. |
| binData | JSON This is a JSON object containing information about card number or token number. |
| binData.pureS2SSupported | Boolean The value for this parameter will be returned false for REDIRECT. |
| result | JSON This is a JSON object containing response of the request and to be used in subsequent steps. |
| result.otpPostUrl | String The parameter will have null value in case of REDIRECT. |
| resutl.acsTemplate | String acsTemplate is a base64 encoded string. The merchant needs to decode acsTemplate, which is an HTML format with auto submit, which then needs to be shown on the customer’s browser. The HTML being auto submit, it will take the customer to the bank page for authentication. |
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 for - S2S Link and Pay.