API Reference
Start typing to search…

Absolute Split After Transaction

You must specify two decimal places for each split, but ensure the sum split amounts are equal to the transaction amount.

📘

Note:

You must specify two decimal places for each split, but ensure the sum of the percentage of all splits is equal to 100.

HTTP Method: POST

Environment

Test Environment<https://test.payu.in/merchant/postservice.php?form=2>
Production Environment<https://info.payu.in/merchant/postservice.php?form=2>

Request parameters

Parameter Description Sample Value

key

string This parameter must include the Merchant key that was provided by PayU.

vDy3i7

command

string The parameter must contain the name of the web service.

payment_split

hash

String The hash string encryption is specified in this parameter. The format of the hash is:
|sha512(key|command|var1|salt)
Where, var1 contains the fields as described in the var1 description.

 

var1

string (JSON) This parameter is in a JSON format and fields included in the JSON format are explained the JSON request structure table.

For an example, refer the Request Structure subsection.

JSON request structure

The var1 parameter is in JSON format. The fields in the JSON format are described in the following table:

Field Description Example

type

The type of split is specified in this field. Use absolute in this field. The absolute amount is specified for each part of the split. The absolute amount is specified in the aggregatorSubAmt field of the JSON for each child or aggregator.

absolute

payuid

The payment identifier provided by PayU for the transaction.

403993715525003544

splitInfo

This parameter must include the list of aggregator sub transaction IDs and sub amounts as specified in the Request Structure for var1 subsection:

  • aggregatorSubTxnId: The aggregator sub transaction ID is specified in this field.
  • aggregatorSubAmt: The aggregator sub amount is specified in this field.
  • aggregatorCharges: The aggregator charges is specified in this field.Note: The aggregatorCharges field can only be used by parent merchant to get the aggregator commission.

Refer to Request Structure for var1 subsection.

Request structure for var1 to be included in payment_split API

{  "type": "absolute",  
    "payuId": "xxxxxxxx", # PayuID of parent transaction which needs to be split.  
   "splitInfo": 
    {    
       "merchantKey1": 
       {
       "aggregatorSubTxnId": "30nknyhkhib",
       "aggregatorSubAmt": "8",
       "aggregatorCharges": "2" // parent merchant commission (Optional)    
       },
      "merchantKey2":
      {
       "aggregatorSubTxnId": "13u0nknou0",
       "aggregatorSubAmt": "2"
      },
       "merchantKey3":
       {
        "aggregatorSubTxnId": "13u0nknou02",
        "aggregatorSubAmt": "2",
        "aggregatorCharges": "1" // parent merchant commission (Optional)
       }
     }
}

Sample response

Sample response for a successful split:

{  
 "status": 1,  
 "message": "Splits creation successful.",  
 "splitStatus": "success",  "splitSegments": 
   [
         {
           "merchantKey": "merchantKey1",
           "amount": 8,
           "subvention_amount": 0,
            "txnId": "30nknyhkhib",
           "additional_charges": 0,
           "transaction_fee": 8    },
           {
             "merchantKey": "merchantKey2",
            "amount": 2,