Collect Payment for WealthTech - Merchant Hosted Integration

This section provides API details for _payment API used for collecting WealthTech payments, specifically designed for mutual fund transaction processing. The API introduces new parameters and validation rules to support wealth management payment flows.

Method: POST
Content-Type: application/x-www-form-urlencoded

Environment


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

Request Parameters

Parameter	Description	Example
key `mandatory`	`String` This parameter is the unique merchant key provided by PayU for your merchant account. For more information, refer to Generate Merchant Key and Salt.	8488225
txnid `mandatory`	`Varchar` This parameter is known as Transaction ID (or OrderID). It is the order reference number generated at your (Merchant's) end. It is an identifier which you(merchant) would use to track a particular order. If a transaction using a particular transaction ID has already been successful at PayU, the usage of same Transaction ID again would fail. Hence, it is essential that you post us a unique transaction ID for every new transaction (Please make sure that the transaction ID being sent to us hasn't been successful earlier. In case of this duplication, the customer would get an error of 'duplicate Order ID').	fd3e847h2
amount `mandatory`	`float` This parameter should contain the payment amount of the particular transaction. Note: Type-cast the amount to float type	10
productinfo `mandatory`	`Varchar` This parameter should contain a brief product description. It should be a string describing the product (The description type is entirely your choice).	T-shirt
firstname `mandatory`	`Varchar` This parameter must contain the first name of the customer.	Ankit
email `mandatory`	`Varchar` This parameter must contain the email of the customer	[email protected]
phone `mandatory`	`Integer` Merchant needs to take the customer's GPay registered phone number and pass in this field. This field will be used for further mapping the customer VPA and initiate a collect request.	9876543210
pg `mandatory`	`String` This parameter contains the payment method to be enabled to collect payment from your customer. For Net Banking, use NB and DC or CC for cards.	NB
bankcode `mandatory`	`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. For the list of bankcodes: * Net Banking: refer to Net Banking Codes * Cards: refer to Card Type Codes and Supported Banks for Cards.	AXIB
surl `mandatory`	`string` The "surl" field is the success URL, which is the page PayU will redirect to if the transaction is successful. The merchant can handle the response at this URL after the customer is redirected there.	https://apiplayground-response.herokuapp.com/
furl `mandatory`	`String` The "furl" field is the Failure URL, which is the page PayU will redirect to if the transaction is failed. The merchant can handle the response at this URL after the customer is redirected there.	https://apiplayground-response.herokuapp.com/
api_version `mandatory`	API version must be posted as `21`	21
hash `mandatory`	`String` The hash calculated by the merchant using the key and salt provided by PayU. The format for calculating the hash: sha512(key\|txnid\|amount\|productinfo\|firstname\|email\|udf1\|udf2\|udf3\|udf4\|udf5\|\|\|\|\|\|SALT) For more information, refer to Generate Hash.	a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0
more_info `mandatory for Wealth Tech`	`JSON` This parameter contains various fields including the Wealth Tech object (wtParams). For more information on wtParams object field, refer to Wealth Tech object (wtParams) fields Description.	Refer to Wealth Tech object (wtParams) fields Description
lastname `optional`	`String` The last name of the customer.	Sharma
address1 `optional`	`String` The first line of the billing address.	123 Main Street
address2 `optional`	`String` The second line of the billing address.	Apartment 4B
city `optional`	`String` The city where your customer resides as part of the billing address.	Mumbai
state `optional`	`String` The state where your customer resides as part of the billing address.	Maharashtra
country `optional`	`String` The country where your customer resides.	India
zipcode `optional`	`String` Billing address zip code is mandatory for the cardless EMI option.	400001
udf1 `mandatory for Cross-Border Payments`	`String` This parameter has been made for you to keep any information corresponding to the transaction. Note: This parameter must contain buyer's PAN number for Cross-Border Payments.	ABCDE1234F
udf2 `optional`	`string` This parameter has been made for you to keep any information corresponding to the transaction.	Additional Info 1
udf3 `mandatory for Cross-Border Payments`	`String` This parameter has been made for you to keep any information corresponding to the transaction.	GSTIN123456
udf4 `optional`	`String` This parameter has been made for you to keep any information corresponding to the transaction.	Additional Info 2
udf5 `optional`	`String` This parameter has been made for you to keep any information corresponding to the transaction.	Additional Info 3
additional_charges `optional`	`String` Collect additional charges for the transaction. For example, platform fee	10.00

Hash Calculation

The hash is calculated using SHA-512 algorithm with the following field sequence:

key|txnid|amount|productinfo|firstname|email|udf1|udf2|udf3|udf4|udf5|udf6|udf7|udf8|udf9|udf10|salt

Hash Generation Steps

Concatenate fields in the specified order using pipe (|) separator
Append the salt at the end
Apply SHA-512 hashing to the concatenated string
Use the resulting hash as the hash parameter

Wealth Tech object (wtParams) fields Description

Sample JSON

"more_info": {
    "wtParams": [
      {
        "type": "mutual_fund",
        "plan": "GD",
        "amount": "50000",
        "option": "G",
        "scheme": "LT",
        "receipt": "77407",
        "mf_member_id": "123445",
        "mf_user_id": "77407",
        "mf_partner": "cams",
        "mf_investment_type": "L",
        "mf_amc_code": "UTB"
      }
    ]
  }

Fields description

These parameters are included within the more_info field as a JSON array under the fiedl wtParams:

Parameter	Description	Example
type `mandatory`	`string` - Transaction type, must be "mutual_fund"	`"mutual_fund"`
amount `mandatory`	`numeric` - Amount in paise, must match order amount	`50000`
receipt `mandatory`	`string` - Unique PG reference number (max 25 chars)	`"77407"`
mf_member_id `mandatory`	`numeric` - Member ID issued by mutual fund platform (5-20 chars)	`"123445"`
mf_user_id `mandatory`	`string` - Unique mutual fund user/client ID (max 10 chars)	`"77407"`
mf_partner `mandatory`	`string` - Mutual fund platform: cams, kfin, bse, nse (max 4 chars)	`"cams"`
mf_investment_type `mandatory`	`string` - Investment type: L (Lump Sum) or S (SIP) (single char)	`"L"`
plan `optional`	`string` - Mutual fund plan name	`"GD"`
folio `optional`	`string` - Unique mutual fund account identifier	`"12345678"`
option `optional`	`string` - Mutual fund plan option	`"G"`
scheme `optional`	`string` - Mutual fund type/scheme	`"LT"`
mf_amc_code `optional`	`string` - Asset Management Company code (max 5 chars)	`"UTB"`

Validation Rules

Mandatory Field Validations

type: Must always be "mutual_fund"
amount: Must match the overall order amount and be in paise
receipt: Must be unique across transactions
mf_member_id: Must be numeric with length between 5-20 characters
mf_user_id: Maximum 10 characters allowed
mf_partner: Must be one of: "cams", "kfin", "bse", "nse"
mf_investment_type: Only "L" (Lump Sum) or "S" (SIP) allowed

Optional Field Validations

mf_amc_code: Maximum 5 characters
receipt: Maximum 25 characters for SIP registration ID

Sample Request

curl -i 'https://test.payu.in/_payment' \
  -H 'accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' \
  -H 'content-type: application/x-www-form-urlencoded' \
  --data-urlencode 'hash=fbc07b5517029242fd97b982816eb372d6501c1...' \
  --data-urlencode 'key=KOEfPI' \
  --data-urlencode 'txnid=7f41f520f71b' \
  --data-urlencode 'api_version=21' \
  --data-urlencode 'amount=50000' \
  --data-urlencode 'productinfo=Mutual Fund' \
  --data-urlencode 'firstname=John' \
  --data-urlencode '[email protected]' \
  --data-urlencode 'phone=9876543210' \
  --data-urlencode 'more_info={"wtParams":[{"type":"mutual_fund","plan":"GD","amount":"50000","option":"G","scheme":"LT","receipt":"77407","mf_member_id":"123445","mf_user_id":"77407","mf_partner":"cams","mf_investment_type":"L","mf_amc_code":"UTB"}]}'

Sample response

Response Handling

After the customer completes or abandons the payment, PayU POSTs back to your return URL with URL-encoded fields (form post). This payload includes the transaction status, txnid, mihpayid, and a hash you must verify (reverse hashing) before trusting the result.

Sample surl/furl payload:

mihpayid=403993715531077182
mode=CC
status=success
unmappedstatus=captured
key=JPM7Fg
txnid=TXN12345
amount=1000.00
productinfo=Pro Plan
firstname=Aditi
[email protected]
phone=9999999999
udf1=
...
udf5=
PG_TYPE=CC-PG
bankcode=CC
bank_ref_num=896193988312194700
field1=...
field9=Transaction is Successful
hash=<response_hash>

mihpayid=403993715531077182
mode=CC
status=failure
unmappedstatus=failed
key=JPM7Fg
txnid=TXN12345
amount=1000.00
productinfo=Pro Plan
firstname=Aditi
[email protected]
phone=9999999999
udf1=
...
udf5=
PG_TYPE=CC-PG
bankcode=CC
bank_ref_num=
field1=
field2=
...
field9=Transaction Failed
error=E000
error_Message=Bank was unable to authenticate
hash=<response_hash>

Response verification using reverse hashing

Verify the response received above by recomputing SHA-512 using the reverse sequence:

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

Compare the computed digest to hash from the POST payload (case-sensitive).
Trust the result only if t

Using Verify Payment API

After you collect payment using _payment API, you get the response from PayU. You must use the txnid (transaction) parameter in the response with Verify Payment API to get the payment status. For more information, refer to Verify Payment API. You will get the following sample response for success/failure scenarios.

Success scenario

{
  "status": 1,
  "message": "Transaction Processed successfully",
  "details": {
    "48101c0c-5265-4c2a-b6d0-e6e73d42809e": {
      "authpayuid": "999990000005920",
      "transactionid": "48101c0c-5265-4c2a-b6d0-e6e73d42809e",
      "amount": "500.00",
      "user_credentials": "o0dEBA:11b341595c...",
      "card_token": "195748c0f4ec4b3093af",
      "payuid": "999990000006473",
      "status": "captured",
      "udf1": "Y",
      "field9": "Transaction is Successful"
    }
  }
}

Failure scenario

{
  "status": 0,
  "message": "Invalid Parameter: mf_partner must be less than or equal to 4 characters."
}

Response Parameters

Success scenario

Parameter	Description	Example
status `mandatory`	`integer` - Response status (1 for success, 0 for failure)	`1`
message `mandatory`	`string` - Response message describing the result	`"Transaction Processed successfully"`
details `mandatory`	`object` - Transaction details object containing specific transaction information	`{}`
authpayuid `mandatory`	`string` - PayU authorization ID	`"999990000005920"`
transactionid `mandatory`	`string` - Unique transaction identifier	`"48101c0c-5265-4c2a-b6d0-e6e73d42809e"`
amount `mandatory`	`string` - Transaction amount in decimal format	`"500.00"`
user_credentials `optional`	`string` - Encrypted user credentials for future transactions	`"o0dEBA:11b341595c..."`
card_token `optional`	`string` - Tokenized card information	`"195748c0f4ec4b3093af"`
payuid `mandatory`	`string` - PayU transaction reference ID	`"999990000006473"`
field9 `optional`	`string` - Additional transaction information	`"Transaction is Successful"`

Error Response Fields

Parameter	Description	Example
status `mandatory`	`integer` - Response status (0 for error)	`0`
message `mandatory`	`string` - Error message describing the issue	`"Invalid Parameter: mf_partner must be less than or equal to 4 characters."`

Request Parameters

Wealth Tech object (wtParams) fields Description

Sample JSON

Fields description

Sample Request

Sample response

Response Handling

Response verification using reverse hashing

Using Verify Payment API

Success scenario

Failure scenario

Response Parameters

Success scenario

Error Response Fields

EXAMPLE QUESTIONS