Web Collect 360
This API will be used to send collect notification to respective PSP App of the user.
Mutual Fund Use case:
Mutual Fund information using which the file to be shared with ICCL needs to be created to be passed in this API as a JSON (Refer request params & API format below).
TPV Use case:
For TPV (Third Party Validation) payerAccountHashes needs to be passed in the request body and the same will be passed back in response along with corresponding values. PayerAccountHashes will be taken as an array so that merchants can send multiple account hashes which will be verified against the account details selected by user shared by NPCI.
PSP will reject the request if the customer makes the payment with a different account details and send a failure callback to the merchant.
Split Settlement Use case:
Merchants must enter the split settlement details in the API calls whenever they want to split the payment and process multiple split settlements. Fields in this object (SplitSettlement) are both required and optional. Merchants can utilize these fields to settle to your vendors/partners by numerous categories, such as AMOUNT, PERCENTAGE, DEFAULT, and LATER, with the maximum flexibility possible.
GST Use case: For Stock & GST Merchants
Validity of a payerVpa can be verified using the Verify VPA API.
The payeeVpa should be a valid PSP generated vpa for the merchant.
If refUrl is passed in request, refCategory becomes essential for the API to work. So it's either both as combination or none.
Header value should be same as of merchantRequestId sent in request body
Merchant generated unique id for the transaction.
Constraint: Max 35 characters alphanumeric, can also contain hyphen(-), dot(.) & underscore(_)
Vpa on which collect request should be triggered.
Example: something@handle.
Constraint: VPA should only contain a-z, 0-9, . (dot), - (hyphen).
Name of the payer.
Constraint: String as returned in the Verify VPA API.
VPA of the merchant to be used for payment.
Example: testmerchant@handle.
Constraint: VPA should only contain a-z, 0-9, . (dot), - (hyphen).
Minutes for which request is valid.
Constraints: A number between 1 to 64800, both inclusive, in String format.
Amount of collect request to be sent.
Constraints: Amount in two decimals. Decimals are mandatory.
Any transaction summary.
Constraints: The transaction note must be alphanumeric, with a minimum length of 1 character and a maximum length of 50 characters.
Defines the purpose code of the transaction.
Constraints: Refer purpose code list.
Defines the initiation mode of the transaction.
Constraints:Refer initiation mode list.
Invoice as sent by merchant in the form of url.
Details for refUrl, whether it is 01(advertisement), 02(invoice)
Current Epoch Unix timestamp string. Has to be of 13 digit in Milliseconds.
Example: 1496918882000.
Merchant Defined Parameters
Example: "{\"udf1\":\"value1\",\"udf2\":\"value2\",…}"
Note: Few special characters are not allowed. Regex for the characters which are not allowed : ^[^/#-()*!%~`]+$
Contains details of Mutual Funds.
Member Id with ICCL or ARN_RIA with RTA.
Client Id with ICCL or USER_CODE with RTA.
One of the below.
NSE, BSE, KFIN, CAMS.
Folio Number of the MF, used for RTA reporting. Mandatory for RTA reporting.
Unique order number of each MF.
Individual MF amount within the array of MF being purchased.
(Amount in two decimals. Decimals are mandatory).
Scheme Code of the MF, used for RTA reporting. Mandatory for RTA reporting.
AMC Code of the MF, used for RTA reporting. Mandatory for RTA reporting.
PAN Number of the user, used for RTA reporting. Mandatory for RTA reporting.
One of the below; LUMPSUM, SIP.
In-house Number of the SIP.
Application Number (Partner Reference Number)- ITRN.
Hashed value of accounts to be passed by merchant for TPV.
Hashing logic:
payerAccountHash = sha256( account Number + first 4 digit of account IFSC)
From account Number the leading zeros should be removed and then the hash should be calculated.
Eg: Account No. = 0000123456789 & IFSC = ABCD0000345
Hash will be calculated on 123456789ABCD.
Split Settlement details of merchant and partners for this transactions.
The type of split for this transaction. Can be AMOUNT, PERCENTAGE, DEFAULT, LATER.
Split share for merchant pool account.
List of partners for which the split needs to be divided with the value.
The LSP id provided by the bank.
Split share for LSP account. Decimal Value.
Split details of GST merchants .
One of the below:
GST Split name
PURCHASE,CASHBACK, DISCOUNT, GST, CGST, SGST, CESS, IGST, GSTINCENTIVE, TIPS, CONFEE, DISCPCT, CONPCT & GSTPCT.
UPI International Split name
BASEAMOUNT,BASECURR,FX&MKUP.
Appropriate split value according to split name.
Invoice name of the order.
Invoice number of the order.
Date of the invoice of the order.
Geographical code from where the txn was initiated.
PSP status of the API.
Example:- Values: SUCCESS | FAILURE
PSP response code for the API.
Values: Refer Codes Guide in Resource Section.
PSP response message for the API.
Values: Refer Codes Guide in Resource Section.
Unique id for the merchant as passed in request headers.
Unique id for the merchant channel as passed in request headers.
Merchant generated unique id for collect request.
Constraint: Max 35 characters & Alphanumeric.
Amount for transaction.
Constraint: Amount in two decimals. Decimals are mandatory.
Vpa on which collect request was triggered.
Name of the payer to whom collect request was sent.
VPA of the merchant to be used for payment.
Merchant Category Code of the payee merchant.
Invoice as sent by merchant or reference to the transaction in the form of url.
Remarks sent by merchant for the collect request.
Timestamp of when collect request was triggered.
Format: YYYY-MM-DDTHH:MM:SS+05:30.
Timestamp of when the collect request will expire.
Format: YYYY-MM-DDTHH:MM:SS+05:30.
UPI request id returned by gateway for the transaction.
Reference id returned by the gateway.
Response status returned by gateway.
Values: SUCCESS | FAILURE.
Response code returned by gateway for the transaction.
Values: 00, Any valid NPCI error code
Response message returned by gateway for the transaction.
Contains details of Mutual Funds (as passed in the request).
Member Id with ICCL or ARN_RIA with RTA.
Client Id with ICCL or USER_CODE with RTA.
One of the below;
Values: NSE, BSE, KFIN, CAMS.
Folio Number of the MF, used for RTA reporting. Mandatory for RTA reporting.
Unique order number of each MF. Oder Number in ICCL or APPL_NO in RTA.
Individual MF amount within the array of MF being purchased.
Constraint: Amount in two decimals. Decimals are mandatory.
Scheme Code of the MF, used for RTA reporting. Mandatory for RTA reporting.
AMC Code of the MF, used for RTA reporting. Mandatory for RTA reporting.
PAN Number of the user, used for RTA reporting. Mandatory for RTA reporting.
One of the below;
Values:LUMPSUM, SIP.
As passed in the request body.
Split Settlement details of merchant and partners for this transactions.
List of partners for which the split needs to be divided with the value.
The LSP id provided by the bank.
Split share for LSP account. Decimal Value.
The type of split for this transaction. Can be AMOUNT, PERCENTAGE, DEFAULT, LATER.
Split share for merchant pool account.
Unique id for subMerchant. Only if present as a subMerchant.
Unique id for the channel via which request is made. Only if present as a subMerchant.
Udf parameters as passed in the request.
Example: "{\"udf1\":\"value1\",\"udf2\":\"value2\",…}"
Have questions?
- Need help? Contact support
- LLM? Read llms.txt

