Collect Payment API - S2S Link and Paypost https://test.payu.in/_paymentForm DatakeyconstenumrequiredThe merchant key is a unique identifier for a merchant account in PayU's database. It is provided by PayU and use your Test key here.JPM7FgJPM7FgAllowed:JPM7FgtxnidintegerrequiredThe transaction ID is a reference number for a specific order that is generated by the merchant. It is used to track the order and must be unique. PayU's system will not accept duplicate transaction IDs.amountnumberrequiredThis field should contain the payment amount for the transaction.productinfostringrequiredThis field should be a string containing a brief description of the product.firstnamestringrequiredThe first name of the customer.emailstringrequiredThe email address of the customer.phoneintegerrequiredThe phone number of the customer.surlstringrequiredThe "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.furlstringrequiredThe "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.hashstringrequiredIt is used to avoid the possibility of transaction tamperingpgconstenumrequiredThe pg parameter determines which payment mode you are using to collect payment.BNPLBNPLAllowed:BNPLbankcodestringrequiredEach payment option is identified with a unique bank code at PayU. The merchant must post this parameter with the corresponding payment option’s bank code value in it.txn_s2s_flowconstenumrequiredThis parameter must be passed with the value as 4 for Legacy Decoupled flow.4Allowed:4LinkAndPayFlowTypestringrequiredThis parameter can contain the value as 1 or 0. If value is 1, then 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 If value is 0, then 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 issuerLinkAndPayFlowDetailsstringrequiredThis field is to include additional details are required from merchant for any payment instrument.user_credentialsstringrequiredUnique user credential mapped against each user, to be passed by the merchant.lastnamestringLast name of the customer (must only contains alphabets).curlstringThe "curl" field is the Cancel URL, which is the page PayU will redirect to if the transaction is canceled by the customer. The merchant can handle the response at this URL after the customer is redirected there.udf1stringUser-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.udf2stringUser-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.udf3stringUser-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.udf4stringUser-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.udf5stringUser-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.HeadersContent-Typeconstenumrequiredapplication/x-www-form-urlencodedapplication/x-www-form-urlencodedAllowed:application/x-www-form-urlencodedResponse 200Updated about 1 month ago