Integration Guide
Start typing to search…

Non-Seamless Integration - TPV

This section describes the step-by-step procedure to integrate TPV with non-seamless flow.

Step 1: Post the payment request with PayU

Environment
Test Environmenthttps://apitest.payu.in/v2/payments
Production Environmenthttps://api.payu.in/v2/payments>
Request headers
ParameterDescription
dateThe current date and time. For example, format of the date is Wed, 28 Jun 2023 11:25:19 GMT.
authorizationThe actual HMAC signature generated using the specified algorithm (sha512) and includes the hashed data. For more information, refer to authorization fields description.

authorization fields description

FieldDescription
usernameRepresents the username or identifier for the client or merchant, for example smsplus.
algorithmUse SHA512 algorithm for hashing and send this as header value.
headersSpecifies which headers have been used in generating the hash, for example date.
signatureThe HMAC signature generated using the specified algorithm. For more information, refer to hashing algorithm.

hashing algorithm

You must hash the request parameters using the following hash logic:

Hash logic: sha512(<Body data> + '|' + date + '|' + merchant_secret)

Where <Body data> contains the request body posted with the request.

Sample header code
var merchant_key = 'smsplus';
var merchant_secret = 'izF09TlpX4ZOwmf9MvXijwYsBPUmxYHD';
// date
var date = new Date();
date = date.toUTCString();

// authorization
var authorization = getAuthHeader(date);

function getAuthHeader(date) {
    var AUTH_TYPE = 'sha512';
    var data = isEmpty(request['data']) ? "" : request['data'];
    var hash_string = data + '|' + date + '|' + merchant_secret;
    var hash = CryptoJS.SHA512(hash_string).toString(CryptoJS.enc.Hex);
    return `hmac username="${merchant_key}", algorithm="${AUTH_TYPE}", headers="date", signature="${hash}"`;
}
Request parameters
Parameter Description Example
accountId
mandatory		 String Merchant key provided by PayU. Character limit: 50 "smsplus"
txnId
mandatory		 String Unique transaction ID for the transaction. Character limit: 50 "REF_123456789"
order
mandatory		 Object Order details containing product information and pricing. See order object {"productInfo": "Product Name", "paymentChargeSpecification": {"price": 1000.00}}
billingDetails
mandatory		 Object Customer billing information. See billingDetails object {"firstName": "John", "email": "[email protected]", "phone": "9876543210"}
callBackActions
mandatory		 Object Callback URLs for different payment outcomes. See callBackActions object {"successAction": "https://merchant.com/success", "failureAction": "https://merchant.com/failure"}
additionalInfo
mandatory		 Object Additional transaction parameters including flow type. For more information, refer to additionalInfo object {"txnFlow": "non-seamless", "enforcePaymethod": "NB"}
beneficiaryDetail
mandatory		 Object JSON object to include TPV beneficiary details. For more information, refer to beneficiaryDetail object For more information, refer to beneficiaryDetail object
beneficiaryDetail Object
Parameter Description Example
beneficiaryName
mandatory		 String Name of the beneficiary account holder. Character limit: 100 "Merchant Account"
beneficiaryAccountNumber
mandatory		 String Bank account number of the beneficiary. Character limit: 50 "1234567890"
beneficiaryAccountType
mandatory		 String Type of beneficiary account (e.g., "SAVINGS", "CURRENT"). Character limit: 20 "SAVINGS"
order Object
Parameter Description Example
productInfo
mandatory		 Product details. Product details
orderedItem
optional		 Details about the items ordered. Array of Objects
userDefinedFields
optional		 Custom fields for additional information. Fields: udf1, udf2, udf3, udf4, udf5, udf6, udf7, udf8, udf9, udf10. For more information, refer to Object
paymentChargeSpecification
mandatory		 Includes amount and charges. For more information, refer to paymentChargeSpecification object fields description Object
paymentChargeSpecification object fields description
Parameter Description Example
price
mandatory		 The transaction amount. 1000
netAmountDebit
optional		 Net amount to be debited. 1000
taxSpecification
optional		 Tax details of the product/order. Object
convenienceFee
optional		 Fees format (e.g., CC:12). CC:12
offers
optional		 Offers applied or available for the payment. Object
userDefinedFields object fields description
FieldDescription
udf1User defined field.
udf2User defined field.
udf3User defined field.
udf4User defined field.
udf5User defined field.
udf6User defined field.
udf7User defined field.
udf8User defined field.
udf9User defined field.
udf10User defined field.
billingDetails Object
Parameter Description Example
firstName
mandatory		 First name of the billing contact. Ashish
lastName
optional		 Last name of the billing contact. Kumar
address1
mandatory		 Primary billing address. 123 Main Street
address2
optional		 Secondary billing address. Apt 4B
phone
optional		 Phone number of the billing contact. 9123456789
email
mandatory		 Email address of the billing contact. [email protected]
city
optional		 City of the billing address. Bharatpur
state
optional		 State of the billing address. Rajasthan
country
optional		 Country of the billing address. India
zipCode
optional		 Postal/Zip code of the billing address. 321028
callBackActions Object
Parameter Description Example
successAction
mandatory		 URL to be called on payment success. https://example.com/success
failureAction
mandatory		 URL to be called on payment failure. https://example.com/failure
cancelAction
mandatory		 URL to be called if user cancels the payment. https://example.com/cancel
codAction
optional		 URL for Cash on Delivery (COD) action. https://example.com/cod
additionalInfo Object
Parameter Description Example
enforcePaymethod
optional		 Force a transaction with a specified method (e.g., CC, DC). CC
createOrder
optional		 A flag to store the order details (true/false). true
txnS2sFlow
optional		 For defining seamless/non-seamless flows in handling payments. nonseamless

Step 2: Check the response from PayU

Updated 5 days ago