Net Banking Integration

Integrate TPV through Net Banking using the procedure described in this section.

Prerequisites

Seamless integration has to be done as per the standard kit. For more information, refer to Collect Payments API under API Reference.

Step 1: List the account numbers

Collect or prepare a list of account numbers that must be posted to PayU for TPV at step 2.

Step 2: Post the parameters to PayU

With the following additional parameters, make the transaction request with the customer’s bank account number to the PayU using the Collect Payment (_payment) API. For more information, refer toCollect Payment API - Merchant Hosted Checkout .
Environment

Request parameters

beneficiarydetail JSON Object Fields

It must contain the list of account numbers and the ifscCode key with the list of corresponding IFSC codes (in the same order as provided in the beneficiaryAccountNumber key). You can post up to five account details in this parameter. For example:

{"beneficiaryAccountNumber":"002001600674|00000031957292212|00000035955239352|00000035955239352",  
"ifscCode":"KTKB0000046|KTKB0000023|KTKB0000035|KTKB0000035"}

Checksum Logic for Hash

The following hash logic must be used for the parameters posted:

📘

beneficiarydetail parameter in hashing:

The beneficiarydetail parameter value will be at last or the last value to be appended.

plaintext

key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3
|udf4|udf5||||||beneficiarydetail|SALT

Step 3: Check the response from PayU

Hash Validation Logic for Payment Response (Reverse Hashing)

While sending the response, PayU takes the exact same parameters that were sent in the request (in reverse order) to calculate the hash and returns it to you. You must verify the hash and then mark a transaction as a success or failure. This is to make sure the transaction has not tampered within the response.

The order of the parameters is similar to the following:

sha512(SALT|status||||||||udf3|udf2|udf1|email|firstname|productinfo|amount|txnid|key)

📘

beneficiarydetail parameter not required in reverse hashing:

The beneficiarydetail parameter should not be present in reverse hashing and order of parameters is similar to the following:

sha512(SALT|status||||||||udf3|udf2|udf1|email|firstname|productinfo|amount|txnid|key)

Response Parameters

The following table describes the parameters in the response from PayU:

📘

Store the mihpayid and txnid parameter values in response:

PayU recommends you to make provisions to store the mihpayid and txnid parameter values (in the response) in your server as proof that TPV has been completed for a customer.

Sample response

Formatted response:

Array
(
    [mihpayid] => 403993715524308236
    [mode] => NB
    [status] => success
    [unmappedstatus] => captured
    [key] => JP***g
    [txnid] => TtEmKjWF2uGliF
    [amount] => 10.00
    [discount] => 0.00
    [net_amount_debit] => 10
    [addedon] => 2021-10-05 12:44:06
    [productinfo] => iPhone
    [firstname] => Ashish
    [lastname] => 
    [address1] => 
    [address2] => 
    [city] => 
    [state] => 
    [country] => 
    [zipcode] => 
    [email] => [email protected]
    [phone] => 9876543210
    [udf1] => 
    [udf2] => 
    [udf3] => 
    [udf4] => 
    [udf5] => 
    [udf6] => 
    [udf7] => 
    [udf8] => 
    [udf9] => 
    [udf10] => 
    [hash] => 74d1039311528b4a7b699db7ce195d6a219d7442271dedb23e516e29490ec743a89c12448698178907e03d32fa05e8178694db8037bc0be53380099e47c3d63f
    [field1] => 
    [field2] => 
    [field3] => 
    [field4] => 
    [field5] => 
    [field6] => 
    [field7] => 
    [field8] => 
    [field9] => Transaction Completed Successfully
    [payment_source] => payu
    [PG_TYPE] => NB-PG
    [bank_ref_num] => 30646df4-69b7-43f4-acdd-21e6a593c037
    [bankcode] => TESTPGNB
    [error] => E000
    [error_Message] => No Error
)

📘

Verify payment:

PayU recommends you. to verify the transaction details using the Verification Payment API. For more information, For API reference, refer to Verify Payment API.