PayU Hosted Checkout - CBpost https://test.payu.in/_paymentForm DatakeyconstenumrequiredMerchant key provided by PayU during onboarding.JPM7FgAllowed:JPM7FgtxnidstringrequiredThe transaction ID is a reference number for a specific order that is generated by the merchant.amountintegerrequiredThe payment amount for the transaction.productinfostringrequiredA brief description of the product.firstnamestringrequiredThe first name of the customer.surlstringrequiredThe success URL, which is the page PayU will redirect to if the transaction is successful.furlstringrequiredThe Failure URL, which is the page PayU will redirect to if the transaction is failed.emailstringrequiredThe email address of the customer.lastnamestringrequiredThe last name of the customer.citystringrequiredThe city name of the customer address.statestringrequiredThe country as part of the customer address.countrystringrequiredDefaults to INThe country name which is part of the customer address. It must be only with the value as "IN" (for India).hashstringrequiredIt 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)phonenumberThe phone number of the customer.buyer_type_businessstringenumDefaults to 1This parameter is used to identify whether it is a B2B transaction. If 1 is posted, it is a B2B transaction.01Allowed:01curlstringThe Cancel URL, which is the page PayU will redirect to if the transaction is cancelled by customer.udf1stringThis 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'sDOBudf2stringUser-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.udf3stringThis 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)udf4stringThis parameter must contain the “MerchantName” passed in udf3 in case of PA2PA integration, for UPI mandate consent and recurring txn, this field should not be passed.udf5stringThis 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.HeadersContent-Typeconstenumrequiredapplication/x-www-form-urlencodedAllowed:application/x-www-form-urlencodedResponse 200Updated 4 months ago