UPI Omnichannel S2S Integration

key
mandatory

String The merchant key is provided by PayU and acts as a unique identifier for a specific merchant account in PayU’s database.
Reference: For more information on how to generate the Key and Salt, refer to any of the following:

Production: Generate Production Merchant Key and Sat.

Test: Generate Test Merchant Key and Salt.

Your Test Key

api_version
optional

String The API version for this API.

1

txnid
mandatory

String The transaction ID is the order reference number generated by the merchant to track a particular order. It can be used only once and PayU’s system does not accept a duplicate Transaction ID.

s7hhDQVWvbhBdN

amount
mandatory

float It should contain the payment amount of the particular transaction. The amount must be greater than Rs. 8000 for the cardless EMI option.

10.00

productinfo
mandatory

String It should be a string containing a brief description of the product.

iPhone

email
mandatory

String The email of the customer.

[email protected]

phone
mandatory

String The phone number of the customer.

9876543210

surl
mandatory

String Success URL(surl) – It must contain the URL on which PayU will redirect the final response if the transaction is successful.

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

furl
mandatory

String Failure URL (furl) – It must contain the URL on which PayU will redirect the final response in case of failure.

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

<glossary:pg>
mandatory

String The payment method is specified in this field. For UPI INTENT, specify parameter as UPI.

UPI

<glossary:bankcode>
mandatory

String Each payment option is identified with a unique bank code at PayU. For UPI Intent, specify the values as INTENT.

INTENT

txn_s2s_flow

enumm The type of transaction flow. This field is mandatory for all types of S2S flows that drive the response types of transactions. For POS, specify the value as 4.

4

firstname
mandatory

String The first name of the customer.

Ashish

lastname
mandatory

String The last name of the customer.

Verma

address1
optional

String The first line of the billing address.

H.No- 17, Block C, Kalyan Bldg, Khardilkar Road, Mumbai

address2
optional

String The second line of the billing address.

34 Saikripa-Estate, Tilak Nagar

city
optional

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

Mumbai

state
optional

String The state where your customer resides as part of the billing address.

Maharashtra

country
optional

String The country where your customer resides.

India

zipcode
optional

String Billing address zip code is mandatory for the cardless EMI option.
Character Limit-20

400004

hash
mandatory

String It is used to avoid the possibility of transaction tampering. For more information, refer to Generate Hash.

eabec285da28fd
0e3054d41a4d24fe
9f7599c9d0b6664
6f7a9984303fd612
4044b6206daf831
e9a8bda28a6200d
318293a13d6c193
109b60bd4b4f8b09
c90972

udf1
optional

String User-defined fields(udf) are used to store any information corresponding to a particular transaction. Merchants can use up to 5 udfs in the post designated as udf1, udf2, udf3, udf4, udf5. For example, you can store customer's preferred payment

Payment Preference

udf2
optional

String User-defined fields(udf) are used to store any information corresponding to a particular transaction. Merchants can use up to 5 udfs in the post designated as udf1, udf2, udf3, udf4, udf5. For example, you can store customer's preferred payment.

Shipping Method

udf3
optional

String User-defined fields(udf) are used to store any information corresponding to a particular transaction. Merchants can use up to 5 udfs in the post designated as udf1, udf2, udf3, udf4, udf5. For example, you can store customer's preferred payment.

Shipping Address1

udf4
optional

String User-defined fields(udf) are used to store any information corresponding to a particular transaction. Merchants can use up to 5 udfs in the post designated as udf1, udf2, udf3, udf4, udf5. For example, you can store customer's preferred payment.

Shipping City

udf5
optional

String User-defined fields(udf) are used to store any information corresponding to a particular transaction. Merchants can use up to 5 udfs in the post designated as udf1, udf2, udf3, udf4, udf5. For example, you can store customer's preferred payment.

Shipping Zip Code

s2s_client_ip
mandatory

String This parameter must have the source IP of the user's device.
Note: This information is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information.

s2s_device_info
mandatory

varchar This parameter must have the user agent of device.
Note: This information is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information.

upiAppName
mandatory

For Specific Intent, merchant should share the app name which is selected by customer on the merchant check-out page. The following are the enum’s expected for major apps:
- phonepe
- googlepay
- paytm
- bhim
- cred
- amazonpay
- whatsapp
- genericintent – For any other app apart from
above

vpa
mandatory

String Virtual Private Address. VPA can first be validated using VPA validate web service. Also, add regex where ‘@’ exists. Example: 8800411088@upi This needs to be passed in case of collect flow of UPI only.

8800411088@upi