Collect Payment API - BNPL Link & Pay

key mandatory

String This parameter is the unique merchant key provided by PayU for your merchant account. For more information, refer to Generate Merchant Key and Salt.

8488225

txnid
mandatory

varchar This parameter is known as Transaction ID (or OrderID). It is the order reference number generated at your (Merchant’s) end. It is an identifier which you(merchant) would use to track a particular order. If a transaction using a particular transaction ID has already been successful at PayU, the usage of same Transaction ID again would fail. Hence, it is essential that you post us a unique transaction ID for every new transaction (Please make sure that the transaction ID being sent to us hasn’t been successful earlier. In case of this duplication, the customer would get an error of ‘duplicate Order ID’).

fd3e847h2

amount
mandatory

float This parameter should contain the payment amount of the particular transaction. Note: Type-cast the amount to float type

10

productinfo
mandatory

varchar This parameter should contain a brief product description. It should be a string describing the product (The description type is entirely your choice).

T-shirt

firstname
mandatory

varchar This parameter must contain the first name of the customer.

Ankit

email
mandatory

varchar This parameter must contain the email of the customer)

[email protected]

phone
mandatory

integer Merchant needs to take the customer’s GPay registered phone number and pass in this field. This field will be used for further mapping the customer VPA and initiate a collect request.

pg
mandatory

string The payment gateway is specified in this parameter. For BNPL, specifiy BNPL.

QR

bankcode
mandatory

string Each payment option is identified with a unique bank code at PayU. You must use any of the following bank code for BNPL:

• LAZYPAY for accepting payments with LAZYPAY card.
• SIMPL for accepting payments with Simpl

UPIQR

surl
mandatory

string 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.

https://apiplayground-response.herokuapp.com/

furl
mandatory

stringThe "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.

https://apiplayground-response.herokuapp.com/

storecard_token_type
mandatory for Saved cards

stringThis parameter is used to specify the store card token type. For this scenario, you must include 0.

store_card_token
mandatory for Saved cards

string This must include the token generated by PayU for the payment instrument.

• *Note**: Either pass PayU token or user credentials with mobile number for customer identification

txn_s2s_flow
mandatory

stringThis parameter must contain the value as 4 for Link & Pay

LinkAndPayFlowType
mandatory

stringThis parameter must contain any of the following:

• 1: auto-debit will be preferred if customer is found already linked for the payment instrument basis result of the API and final captured / failure response will be returned
• 0: the request will be considered as a standard native OTP request and transaction in progress response will be returned with OTP sent to the customer by the issuer

LinkAndPayFlowDetails
mandatory

This field is to include additional details are required from merchant for any payment instrument.

user_credentials
mandatory

stringThis parameter must contain an unique user credential mapped against each user, to be passed by the merchant.

hash
mandatory

string The hash calculated by the merchant using the key and salt provided by PayU. The format for calculating the hash: ``` sha512(key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3|udf4|udf5||||||SALT)

For more information, refer to [Generate Hash](doc:hashing-request-and-response).

lastname
optional

stringThe last name of the customer.

address1
optional

stringThe first line of the billing address.

address2
optional

stringThe second line of the billing address.

city
optional

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

state
optional

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

country
optional

stringThe country where your customer resides.

zipcode
optional

stringBilling address zip code is mandatory for the cardless EMI option.

udf1

stringThis parameter has been made for you to keep any information corresponding to the transaction.

udf2
optional

string This parameter has been made for you to keep any information corresponding to the transaction.

udf3
optional

string This parameter has been made for you to keep any information corresponding to the transaction.

udf4
optional

string This parameter has been made for you to keep any information corresponding to the transaction.

udf5
optional

string This parameter has been made for you to keep any information corresponding to the transaction.

mihpayid

It is a unique reference number created for each transaction at PayU’s end. You must note this transaction ID as this will be used as a reference for all the future actions on this transaction like Inquiry or Refund.

mode

This parameter describes the payment category by which the transaction was completed or attempted by the customer. For the payment categories, refer to Payment Mode Codes.

status

This parameter gives the status of the transaction as either success, failed or pending.
Possible values: success, failure, pending
If the value of the ‘status’ parameter is ’success’, the transaction is successful.
If the value of ‘status’ is ‘failure’ or ‘pending’, must be treated as a failed transaction only.

key

This parameter contains the merchant key for the merchant’s account at PayU. It would be the same as the key used while the transaction request is being posted from the merchant’s end to PayU.

txnid

This parameter would contain the transaction ID value posted by the merchant during the transaction request.

amount

This parameter would contain the original amount which was sent in the transaction request by the merchant.

productinfo

This parameter would contain the same value of product information which was sent in the transaction request from the merchant’s end to PayU.

firstname

This parameter would contain the same value of first name which was sent in the transaction request from the merchant’s end to PayU.

lastname

This parameter would contain the same value of last name which was sent in the transaction request from the merchant’s end to PayU.

email

This parameter would contain the same value of email which was sent.

phone

This parameter would contain the same value of phone which was sent in the transaction request from the merchant’s end to PayU.

udf

This parameter would contain the same value of udf values that were sent in the transaction request from the merchant’s end to PayU. It ranges from udf1 to udf5.

hash

PayU calculates the hash using a string of other parameters and returns it to the merchant. The merchant must verify the hash, and only then mark a transaction as success/failure. This is to make sure that the transaction hasn’t been tampered with.
The calculation is as follows:
sha512(SALT|status|udf5|udf4|udf3|udf2|udf1|email|firstname|productinfo|amount|txnid|key)
 
Note: The handling of udf1 – udf5 parameters remains similar to the hash calculation when the merchant sends it in the transaction request to PayU. If any of the udf (udf1-udf5) was posted in the transaction request, it must be taken in hash calculation also.
If none of the udf parameters were posted in the transaction request, they should be left empty in the hash calculation too.

error

For the failed transactions, this parameter provides the reason for 
failure.
 
Note: The reason for failure depends upon the error codes provided by different banks and hence the detailing of error reasons may differ from one transaction to another. The merchant can use this parameter to retrieve the reason for failure for a particular transaction.

bankcode

This parameter contains the code indicating the payment option used for the transaction. For example, in the Debit Card mode, there are different options like Visa Debit Card, Mastercard, Maestro etc. For each option, a unique bank code exists. It would be returned in this bank code parameter. For example, Visa Debit Card – VISA, Master Debit Card – MAST.

PG_TYPE

This parameter gives information on the payment gateway used for the transaction. For example, if CC PG was used, it would contain the value CC-PG. Similarly, it would have a unique value for all different types of payment gateways.

bank_ref_num

For each successful transaction – this parameter would contain the bank reference number generated by the bank.

unmappedstatus

This parameter contains the status of a transaction as per the internal database of PayU. PayU’s system has several intermediate status which are used for tracking various activities internal to the system. For more information, refer to Status Explanations.

customerLinked

This parameter contains the status of the customer linking on the merchant. The values can be: 

True: If customer is linked  

False: If customer is not linked

payuToken

This is the value of the payu token which is mapped against a payment instrument