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

Make Payment using Web Checkout Integration
Update Invoice ID [Optional]
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:

Environment

Test	https://test.payu.in/_payment
Production	https://secure.payu.in/_payment

Request Parameters

Parameter	Description	Example
firstname `mandatory`	`String` The first name of the customer.	Ashish
address1 `mandatory`	`String` The first line of the billing address. 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.	H.No- 17, Block C, Kalyan Bldg, Khardilkar Road, Mumbai
address2 `mandatory`	`String` The second line of the billing address.	34 Saikripa-Estate, Tilak Nagar
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 Merchant Hosted Checkout integration`	`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. The payment gateway value for each payment category are listed below. Refer to the following sections for integration with various payment modes: Collect Payments with Net Banking Collect Payments with Card Note: Only the Net Banking and Cards are supported payment methods for Cross-Border payments.	CC
bankcode `mandatory for Merchant Hosted Checkout integration`	`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
udf1 `mandatory`	`String` The Permanent Account Number of the buyer must be collected in this field.	AELPR****E
udf3 `mandatory`	`String` The date of birth of the buyer must be collected using this field in the DD-MM-YYYY format.	02-02-1980
udf5 `mandatory`	`String` The invoice ID or invoice number must be collected using this field.	098450845
txn_s2s_flow `mandatory for S2S integration`	`String` Pass the value as 4 for S2S flow.	4

Note: Before going live in the Production environment, PayU recommends you use the test card or Net Banking credentials before integration. For more information on test card number or Net Banking credentials, refer to Test Cards and UPI ID.

Sample Request & Response

The request and response is similar to PayU Hosted Checkout or Merchant Hosted Checkout Integration. For a sample request and response, refer to Integrate with PayU Hosted Checkout or Integrate with Merchant Hosted Checkout Integration.

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.