CB - NB

post

https://test.payu.in/_payment

PayU allows you to collect cross-border payments using Net Banking. The buyer_type_business parameter is used for Cross Border payment transactions to indicate the type of business of the buyer.

After the payment is complete, you must use the Invoice Upload API to upload the invoices for banks processing.

Environment

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

Sample request

curl -X POST "https://test.payu.in/_payment" \
-H "accept: application/json" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "key=JP***g&txnid=xdB9G7qYpfqszo&amount=10&firstname=PayU User&[email protected]&phone=9876543210&productinfo=iPhone&pg=TESTPG&bankcode=TESTPGNB&surl=https://apiplayground-response.herokuapp.com/&furl=https://apiplayground-response.herokuapp.com/&hash=649bc87e0e8ee7bbd1e930d43c99a9165eb9fa7a3f4542a33e8d66bd207a63d631708fd9781e56b133581f7dabeaa67baa5609d5e5c9990f986792d59e7d41cb"

Sample response

Array
(
    [mihpayid] => 403993715523409521
    [mode] => NB
    [status] => success
    [unmappedstatus] => captured
    [key] => JP***g
    [txnid] => 5jJ9xRceXX1ydT
    [amount] => 10.00
    [discount] => 0.00
    [net_amount_debit] => 1000
    [addedon] => 2021-07-02 15:03:50
    [productinfo] => iPhone
    [firstname] => PayU User
    [lastname] => 
    [address1] => 
    [address2] => 
    [city] => 
    [state] => 
    [country] => 
    [zipcode] => 
    [email] => [email protected]
    [phone] => 9876543210
    [udf1] => 
    [udf2] => 
    [udf3] => 
    [udf4] => 
    [udf5] => 
    [udf6] => 
    [udf7] => 
    [udf8] => 
    [udf9] => 
    [udf10] => 
    [hash] => 716f92a6452adadba68d133ba7f5ca3f3403f03f554e3ef850911f3e6727ee73402b249054170ad276c8b55ca12368a5e27cc69ffb0642ef6403dae9a5708794
    [field1] => vpa-anything@payu
    [field2] => 5jJ9xRceXX1ydT
    [field3] => 
    [field4] => PayU User
    [field5] => AXIhh4ExnaJ9dKiJvPxsewHwxMMmT3ba7UY
    [field6] => 
    [field7] => Transaction completed successfully
    [field8] => 
    [field9] => Transaction completed successfully
    [payment_source] => payu
    [PG_TYPE] => NB-PG
    [bank_ref_num] => 5jJ9xRceXX1ydT
    [bankcode] => NB
    [error] => E000
    [error_Message] => No Error
)

Response parameters

Request parameters

Additional info for request parameters

Payment Request Parameters

The payment request parameters include standard fields like key, txnid, amount, firstname, email, phone, and productinfo. For UPI payments, the following specific parameters are important:

pg: Set to "NB" to indicate Net Banking payment method
bankcode: Set to corresponding bank code. For more information, refer to Net Banking Codes

For a comprehensive list of all parameters and their descriptions, refer to the following:

📘
Reference: For the character limit of each parameter and detailed description, refer to Additional Info for Payment APIs.

❗️
Error handling: If any error message is displayed with an error code, refer to the Error Codes section to understand the reason for these error codes.

Form Data

key

const

enum

required

Merchant key provided by PayU during onboarding.

Allowed:

txnid

string

required

The transaction ID is a reference number for a specific order that is generated by the merchant.

amount

integer

required

The payment amount for the transaction.

productinfo

string

required

A brief description of the product.

firstname

string

required

The first name of the customer.

surl

string

required

The success URL, which is the page PayU will redirect to if the transaction is successful.

furl

string

required

The Failure URL, which is the page PayU will redirect to if the transaction is failed.

string

required

The email address of the customer.

const

enum

required

The pg parameter determines which payment tabs will be displayed on the PayU page. For Net Banking, use NB.

Allowed:

bankcode

const

enum

required

Each payment option is identified with a unique bank code at PayU. For Net Banking bank codes, refer to the Net Banking Codes section

Allowed:

hash

string

required

It is the hash calculated by the merchant. The format for calculating the hash: sha512(key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3|udf4|udf5||||||SALT)

phone

number

The phone number of the customer.

lastname

string

The last name of the customer.

buyer_type_business

string

This parameter is used to identify whether it is a B2B transaction. If 1 is posted, it is a B2B transaction

curl

string

The Cancel URL, which is the page PayU will redirect to if the transaction is cancelled by customer.

udf1

string

This parameter must contain the buyer’s PAN (Permanent Account Number). If the transaction is of UPI mandate or UPI recurring then udf1 should contain the “Buyer's PAN and date of birth in the following format (separated by two pipe characters): Buyer's PAN||Buyer's DOB

udf2

string

User-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.

udf3

string

This parameter must contain the buyer’s DOB. If the transaction is of UPI mandate or UPI recurring then udf1 should contain the “invoice ID of the transaction (generated by the merchant) and merchant name in the following format (separated by two pipe characters): InvoiceID||MerchantName” (where, MerchantName is required for PA2PA integrations only)

udf4

string

This parameter must contain the “MerchantName” passed in udf3 in case of PA2PA integration, for UPI mandate consent and recurring transaction, this parameter value should not be passed.

udf5

string

This parameter must contain the “invoiceId” for every merchant, this field is mandatory during or after the transaction(using the udf_update API post successful transaction.

Response

Environment

Request parameters

Payment Request Parameters

200

EXAMPLE QUESTIONS