This section describes the request and response parameters with sample request and response for UPI One-Time mandate Intent and Collect flow. For more information on integration, refer to UPI One-Time Mandate.
Note
Currently, PayU supports UPI One-Time Mandate only for the Seamless integration.
Request Parameters
Parameter | Description | Example |
---|---|---|
key
|
| Your Test Key |
txnid
|
| fd3e847h2 |
amount |
| 1000 |
productinfo |
| Time Magazine Subscription |
firstname |
| Ashish |
email |
| |
phone |
This information is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information Also, MIS reporting is shared with few issuing banks where email and mobile number is used to keep track of users using SI transactions. | 9843176540 |
surl | surL is the acronym for Success URL. This parameter must contain the URL on which PayU will redirect the final response if the transaction is successful. | |
furl | furl is the acronym for for Failure URL. This parameter must contain the URL on which PayU will redirect the final response if the transaction is failed. | |
pg | It defines the payment category for which you wish to perform UPI One-Time Mandate. For UPI, pg= UPI | UPI |
bankcode | It defines the bank with which you wish to perform UPI using the bank code. Use UPI or INTENT according to the use case. |
|
vpa | This parameter contains the customer’s VPA handle. For the list UPI handles supported, refer to UPI Handles The merchant is advised to check the validity of the VPA through using the VPA Validation API. PayU extends support for the same if required. For more information on using VPA Validation API, refer to  Validate VPA API. | abc@payu |
txn_s2s_flow | This parameter must be passed with the values as 4 for UPI Intent. | 4 |
pre_authorize | This parameter is set to1 to pre-authorize payment. | |
si_Details | This parameter contains the following information in JSON format:
| {"paymentStartDate":"2024-07-24","paymentEndDate":"2024-07-28"} |
hash | Hash is a crucial parameter used to ensure that any date is not tampered while redirecting customer from the merchant website to PayU’s payment interface while registration transactions. It is SHA512 hash generated by encrypting values of merchant key, txnid, amount, productinfo, firstname, email, udf and si_details by merchant salt. In the case of registration transaction, the formula is used to calculate this hash is similar to the following: |
Sample request
Intent Flow
ample request:
curl --request POST
--url https://test.payu.in/_payment
--header 'accept: text/plain'
--header 'content-type: application/x-www-form-urlencoded'
--data key=JPM7Fg
--data pg=UPI
--data bankcode=INTENT
--data txn_s2s_flow=4
--data txnid=aso6787
--data siDetails="{"paymentStartDate": "2019-09-01","paymentEndDate": "2019-12-01"}"
--data pre_authorize=1 \
--data amount=100.00
--data productinfo=iPhone
--data firstname=Ashish
--data [email protected]
--data phone=9876543210
--data surl=https://apiplayground-response.herokuapp.com/
--data furl=https://apiplayground-response.herokuapp.com/
--data hash=8e8de8a3cf2ba999e16c0ffdb63a645074af4ad1aa0a8d66d81555a119c004e1791173fe6199084f256623664b250d3aeb50fc2c4cfc155e729d8811a157c98b
Collect Flow
curl --request POST
--url https://test.payu.in/_payment
--header 'accept: text/plain'
--header 'content-type: application/x-www-form-urlencoded'
--data key=JPM7Fg
--data pg=UPI
--data bankcode=UPI
--data vpa=anything@payu
--data txn_s2s_flow=4
--data txnid=aso6787
--data siDetails="{"paymentStartDate": "2019-09-01","paymentEndDate": "2019-12-01"}"
--data pre_authorize=1 \
--data amount=100.00
--data productinfo=iPhone
--data firstname=Ashish
--data [email protected]
--data phone=9876543210
--data surl=https://apiplayground-response.herokuapp.com/
--data furl=https://apiplayground-response.herokuapp.com/
--data hash=8e8de8a3cf2ba999e16c0ffdb63a645074af4ad1aa0a8d66d81555a119c004e1791173fe6199084f256623664b250d3aeb50fc2c4cfc155e729d8811a157c98b
Sample response
Intent Flow
Success scenario
For Intent, as part of response, Intent URL is returned. Now, merchant needs to use data received in intentURIData parameter, JSON decode the response and use URL to invoke intent at their end
{
"metaData": {
"message": null,
"referenceId": "c5161bae370de1bd4fb886c6c66567a8",
"statusCode": null,
"txnId": "a7440cc636e747b635df",
"txnStatus": "pending",
"unmappedStatus": "pending"
},
"result": {
"paymentId": "99900000000001875",
"merchantName": "Name409208872",
"merchantVpa": "paytmqr@icici",
"amount": "10000.00",
"acsTemplate": "PGh0bWw+PGJvZHk+PGZvcm0gbmFtZT0icGF5bWVudF9wb3N0IiBpZD0icGF5bWVudF9wb3N0IiBhY3Rpb249Imh0dHBzOi8vcHA3OHNlY3VyZS5wYXl1LmluLzY1OWFjNWRhNWUyZjlmNzM1NzhkZWYwYzVjNDM2MWFmOWJhMGVkYmExYjk3NDg2Mjg3ZDI2MzBjZDg1YmU3NWEvaW50ZW50U2VhbWxlc3NIYW5kbGVyLnBocCIgbWV0aG9kPSJwb3N0Ij48aW5..."
},
"otpPostUrl": "https://pp78secure.payu.in/ResponseHandler.php"
}
}
Failure scenario
For Intent, as part of response, Intent URL is returned. Now merchant needs to use data received in intentURIData parameter, JSON decode the response and use URL to invoke intent at their end
Once the transaction is authorised by the customer, PayU will receive confirmation. Same will be passed to the merchant as webhook
{
"metaData": {
"message": "Transaction failed due to invalid params shared by the merchant",
"referenceId": "dde7096af9db932a9fd09b9b4383d8be",
"statusCode": "E1101",
"txnId": "0c4931ddee7a4f69227f",
"txnStatus": "failed",
"intentURIData": "upi://mandate?pa=payu24@icici&pn=Payu&tr=EZM2024042211452400151942&am=10000.00&cu=INR&orgid=400011&mc=6012&purpose=01&tn=Upi%20Mandate&validitystart=22042024&validityend=21052024&amrule=MAX&Recur=ONETIME&Rev=N&Share=Y&Block=Y&txnType=CREATE&mode=13",
"unmappedStatus": "failure"
},
"result": {}
}
Collect Flow
Success scenario
{
"metaData":{
"message":null,
""referenceId":"c5161bae370de1bd4fb886c6c66567a8",
"statusCode":null,
""txnId":"a7440cc636e747b635df",
""txnStatus":"pending",
""unmappedStatus":"pending"
},
"result":{
"postToBank":{
"useMethodGet":true
},
"issuerUrl":"https://api.payu.in/ public/#/c5161bae370de1bd4fb886c6c66567a8/upiLoader"
}
}
Failure scenarios
{
"metaData":{
"message":"Transaction failed due to invalid params shared by the merchant",
"referenceId":"dde7096af9db932a9fd09b9b4383d8be",
"statusCode":"E1101",
"txnId":"0c4931ddee7a4f69227f",
"txnStatus":"failed",
"unmappedStatus":"failure"
},
"result":{
}
}