Integrate Import for PayUBiz

The cross-border payment integration for PayUBiz involves the following significant steps:

  1. Make Payment using Web Checkout Integration
  2. Update Invoice ID [Optional]
  3. Upload Invoice with PayU

Step 1: Make Payment using Web Checkout Integration

The following parameters (mandatory) must be posted using any of the following Web Checkout integration and refer to the corresponding section of Web Checkout Integration documentation for the complete list of parameters to be posted:

Request parameters

The following are the additional request parameter required for cross-border payments with all of the above integrations.

Environment

ParameterDescriptionExample
key mandatoryStringMerchant key provided by PayU during onboarding.Β JPg****f
txnid mandatoryStringThe transaction ID is a reference number for a specific order that is generated by the merchant.Β ypl938459435
amount mandatoryStringThe payment amount for the transaction.10.00Β 
productinfo
mandatory
StringA brief description of the product.Β iPhone
firstname
mandatory
String The first name of the customer.Ashish
lastname
mandatory
String The last name of the customer.Kumar
email
mandatory
StringThe email address of the customer.Β [email protected]
phone
mandatory
StringThe phone number of the customer.Β 
address1
mandatory
StringΒ The first line of the billing address.
H.No- 17, Block C, Kalyan Bldg, Khardilkar Road, Mumbai
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.
34 Saikripa-Estate, Tilak Nagar
address2
mandatory
StringΒ The second line of the billing address.
city
mandatory
StringΒ The city where your customer resides as part of the billing address.Mumbai
state
mandatory
StringΒ The state where your customer resides as part of the billing address,Maharashtra
country
mandatory
StringΒ The country where your customer resides.India
zipcode
mandatory
StringΒ Billing address zip code is mandatory for the cardless EMI option.
`Character Limit-20
400004
pg
mandatory for seamless/s2s flow
StringΒ It defines the payment category that the merchant wants the customer to see by default on the PayU’s payment page. If this field is empty, the system assumes the credit card payment option by default.CC, NB or UPI
bankcode
mandatory for seamless/s2s flow
StringΒ Each 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.AMEX
ccnum
mandatory for cards
String Use 13-19 digit card number for credit/debit cards (15 digits for AMEX, 13-19 for Maestro) and validate with LUHN algorithm. Refer to Card Number Formats and display error message on invalid input.
ccname
mandatory for cards
String This parameter must contain the name on card – as entered by the customer for the transaction.
ccvv
mandatory for cards
String Use 3-digit CVV number for credit/debit cards and 4-digit security code (4DBC/CID) for AMEX cards.
ccexpmon
mandatory for cards
String This parameter must contain the card’s expiry month – as entered by the user for the transaction. It must always be in 2 digits or in MM format. For months 1-9, this parameter must be appended with 0 – like 01, 02…09. For months 10-12, this parameter must not be appended – It should be 10,11 and 12 respectively.
ccexpyr
mandatory for cards
String This parameter must contain the card’s expiry year – as entered by the customer for the transaction. It must be of four digits.
surl
mandatory
String The success URL, which is the page PayU will redirect to if the transaction is successful.
furl
mandatory
StringThe Failure URL, which is the page PayU will redirect to if the transaction is failed.
udf1
mandatory if AD bank request this detail
StringΒ The Permanent Account Number of the buyer must be collected in this field.AELPR****E
udf3
mandatory if AD bank request this detail
String The date of birth of the buyer must be collected using this field in the DD-MM-YYYY format.02-02-1980
udf4
mandatory for payment aggregators
String This parameter must include end merchant legal entity name.XYZ Pvt. Ltd.
udf5
mandatory
StringThe invoice ID or invoice number must be collected using this field.098450845

Sample request

curl --location '
https://test.payu.in/_payment'
\
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'key=JP***g' \
--data-urlencode 'txnid=my_order_9524' \
--data-urlencode 'amount=23' \
--data-urlencode 'productinfo=af' \
--data-urlencode '[email protected]' \
--data-urlencode 'phone=9044782113' \
--data-urlencode 'user_credentials=QyT13U:12345' \
--data-urlencode 'hash={{hash}}' \
--data-urlencode 'surl=https://test.payu.in/admin/test_response' \
--data-urlencode 'furl=https://test.payu.in/admin/test_response' \
--data-urlencode 'udf1=ABCDE1234K' \
--data-urlencode 'udf2=--' \
--data-urlencode 'udf3=02-02-1980' \
--data-urlencode 'udf4=Seller1' \
--data-urlencode 'udf5=INV002131-ASDF-1231' \
--data-urlencode 'firstname=as' \
--data-urlencode 'lastname=kr' \
--data-urlencode 'address1=308,third floor' \
--data-urlencode 'address2=testing' \
--data-urlencode 'city=ggn' \
--data-urlencode 'state=UP' \
--data-urlencode 'country=IND' \
--data-urlencode 'zipcode=122018'

Step 2: Update Invoice ID [Optional]

If the Invoice ID value was unavailable when posting the transaction at Step 1, it can be updated using the UDF Update API by posting it in the UDF5 parameter.Β For more information, refer to UDF Update API.

Step 3: Upload the Invoices

According to the RBI guidelines, the invoice file must be shared with PayU within 10 days of the transaction. The invoices can be uploaded using the Invoice Upload API. For more information, refer to Invoice Upload API.