post https://payusandbox-kong.pc.enstage-sas.com/hexappiuat/api/v2/qa/payuppi/odrService/api/odr/v2/createservicerequest
The Create Service Request API is used to raise a successful dispute service request, it creates a request for a particular transaction sent in the request with the proper reason to raise a request. If raised successfully, this API shares the generated service request and its details in its response.
Environment
| Sandbox | https://payusandbox-kong.pc.enstage-sas.com/api/odr/v2/createServiceRequest |
| Production | Contact your WIBMO KAM or support. |
Sample request
curl --request POST \
--url https://payusandbox-kong.pc.enstage-sas.com/hexappiuat/api/v2/qa/payuppi/odrService/api/odr/v2/createservicerequest \
--header 'X-Consumer-Custom-ID: 8654891RYY57Q0C54329BAD9C7A2DU0G1' \
--header 'bankId: 6060' \
--header 'clientId: 2040' \
--header 'content-type: application/json' \
--header 'entityId: 100' \
--header 'secureCode: FSeAh0yFMopKgU6UNuYLk6' \
--header 'x-api-key: 4A02C4267C9A97A1488AB3259FD1A725' \
--data '
{
"token": "U+IrMhO6ah2GUXOkMLYIwc++wkJZHYJ3s9Xux+qw8U8nlnPs5Yg00tXpGronm5OPs9vYMxaQ7v23KR8SYSfqrjnCuJwsGF8Np3Ujlasbm+abukdLt0ord0Es36AzlBSaLX7Eq9khCcye2DAa5a6nFl3+IsQPUacRN0CB8vz06JrGZ6iXrMk5/7O9rnHXzKMrMimddP0oKIoXfCNdeVflOpTGFLJX+71MdoiVbun2SQ//Do/uXiTEodN9NSqMuYaqZMzBHPB7uLo+XFe4TFrq5a3j2/LAoFzKh13AISN2bkGpiYj3bKr7E1QhXrQIpCopl3JYLzNkGcvlOCzs3aATczY+CxqVPbNjBm1WCXyQkAi3aswCxiHwenMYB9GidHrBUCo3sarBNRn48GK8/LQDMFCcvTjcyDBcVrn8YzVfIOTkwk69cgStQjKf1efb+5xeTGpHDwrAWE/k4ifFs3gadq5k8nnNSkPy4dhv1RGhFHAfeUsy9aDbHjTPDvJtQP1m"
}
'
Response parameters (Decrypted)
This API will provide a token in the response that must be decrypted using the Decrypt API. The decrypted response is similar to the following:
| Parameter | Type | Parameter Requirement | Description |
|---|---|---|---|
| bankId | numeric(4) | Conditional | Value echoed from the request. |
| clientTxnId | String(100) | Mandatory | Unique ID generated by the calling application for each API request. |
| responseCode | String(4) | Mandatory | Contains the status of the transaction. |
| responseMessage | String (15) | Mandatory | Response message based on the response code. |
| serviceRequestNo | numeric(4) | Conditional | A Unique ID generated for each service request. |
| responseDateTime | numeric(14) | Mandatory | Response date time in the format YYYYMMDDHHMMSS with time in 24-hour format |
Sample response (Decrypted)
{
"responseCode": "00",
"responseMessage": "Success",
"responseDateTime": "12-12-2023 16:35:33",
"bankId": 6010,
"clientTxnId": "test131",
"serviceRequestNo": 101
}
Error codes
| Error Code | Description |
|---|---|
| 00 | SUCCESS |
| 03 | INVALID REGISTERED MOBILE NUMBER |
| 04 | INVALID BENEFICIARY MOBILE NUMBER |
| 05 | INVALID REGISTERED EMAIL ID |
| 06 | ALREADY OPEN SERVICE REQUEST EXIST FOR THE GIVEN TRANSACTION |
| 08 | ALREADY SERVICE REQUEST HAS BEEN SETTLED FOR THE GIVEN TRANSACTION |
| 12 | INTERNAL SERVER ERROR |
| 14 | REJECTED SERVICE REQUEST COUNT EXCEEDED FOR THE GIVEN TRANSACTION |
| 155 | SERVICE UNAVAILABLE |
| 1001 | CARD NOT FOUND |
| 1303 | CUSTOMER DETAILS NOT PRESENT |
| 1304 | MORE THAN ONE CUSTOMER IDENTIFIER NOT ALLOWED |
| 9004 | INVALID FIELD FORMAT |
| 9007 | INVALID BANK ID |
| 9008 | INVALID CLIENT ID |
| 9009 | BANK CLIENT ID MISMATCH |
| 9010 | REQUEST SOURCE IS MANDATORY |
| 9011 | REQUEST SOURCE CAN EITHER BE CSR OR API |
| 9012 | TRANSACTION ID IS MANDATORY |
| 9013 | TRANSACTION ID SHOULD CONTAIN ONLY NUMBERS |
| 9014 | DISPUTE COMMENT IS MANDATORY |
| 9015 | DISPUTE REASON ID IS MANDATORY |
| 9016 | TRANSACTION AMOUNT IS MANDATORY |
| 9017 | INVALID TRANSACTION AMOUNT |
| 9018 | TXN DATE TIME IS MANDATORY |
| 9019 | INVALID TXN DATE FORMAT |
| 9020 | CLIENT TXN ID IS MANDATORY |
| 9021 | INVALID CLIENT TXN ID |
| 9023 | DISPUTE REASON ID NOT CONFIGURED |
| 9024 | TRANSACTION ID MISMATCH FOR GIVEN DETAILS |
| 9025 | TRANSACTION ID NOT PRESENT IN DB |
| 9026 | INVALID TXN DATE |
| 9027 | NO UNIQUE IDENTIFIER PROVIDED |
| 9028 | INVALID CUSTOMER ID |
| 9029 | INVALID DISPUTE COMMENT |
| 9029 | INVALID DISPUTE COMMENT |
| 9030 | INVALID MOBILE NUMBER |
Request parameters
Reason IDs
| Reason ID | Description |
|---|---|
1 | I did not do this transaction |
2 | I have been billed multiple times for the same transaction |
3 | I still have not received my refund |
4 | Money got debited from my account but merchant did not receive payment |
5 | Mismatch between amount debited from my A/C and amount billed by the merchant |
6 | Goods or Services Not Provided / Not Received |
7 | Others |
8 | Transaction drop |
9 | Amount not credited back to source |
10 | Cash back queries |
11 | Delay in loading of wallets |
12 | Related to Fees/charges/disclosures |