post https://uatmea-iss-apigw.creditpluspinelabs.com/deviceapi/apis/v1/services/transactions/payment
This API is used to process credit card bill payment requests. The Credit+ Issuing system receives, validates and processes the request. If the request is successful, the cardholder will receive the bill payment message in response. If the request fails, the system returns the corresponding error code. The system sends the successful response only if the request message passes on all input parameters and the payment transaction is processed successfully. A failure response is sent if any of the request message parameters fail in validation/pre-screening checks. Further, it is also sent if all the request message parameter validation are successful; however, the payment transaction couldn't be processed successfully.
HTTP Status and Response Status Matrix
- HTTP Code: This is the response status code issued by a server in response to a client's request made to the server.
- Error Code: This is the error code returned by Credit+ Issuing application in the ‘code’ field of the response message indicating if the request was processed successfully or failed.
- Reason: This is the description of the error code returned by Credit+ Issuing application.
| HTTP Code | Error Code | Reason |
|---|---|---|
| 201 | 000 | Request processed successfully |
| 400 | 997 | Payment Transaction Request failed: invalid request |
| 403 | 900 | Invalid User |
| 404 | 998 | Device(s) does not exist |
| 500 | 999 | Invalid Request Type |
| 400 | 997 | Form Factor Type field is mandatory. |
| 400 | 997 | Form Factor Type field is invalid. |
| 400 | 997 | Form Factor field is mandatory. |
| 400 | 997 | Form Factorfield should be numeric for Form Factor Type 'CRD'. |
| 400 | 997 | Form Factor field should be alphanumeric and without space for Form Factor Type 'ACT'. |
| 400 | 997 | Transaction Type field is mandatory. |
| 400 | 997 | Transaction Type field is invalid. |
| 400 | 997 | Transaction Code field is mandatory. |
| 400 | 997 | Transaction Code field is invalid. |
| 400 | 997 | Transaction Amount field is mandatory. |
| 400 | 997 | Transaction Amount field must be a positive value with maximum scale 14 integers and precision 7 fractions. |
| 400 | 997 | Transaction Currency industry standard code is mandatory. |
| 400 | 997 | Transaction Currency field value must have max length 3. |
| 400 | 997 | Transaction Reference Number field is mandatory. |
| 400 | 997 | Transaction Reference Number field is not allowed for Transaction Type Original. |
| 400 | 997 | MICR Code field should be numeric. |
| 400 | 997 | Cheque Number field is mandatory. |
| 400 | 997 | Cheque Number field value must have size 6. |
| 400 | 997 | Cheque Number field should be numeric. |
| 400 | 997 | Cheque Date field is mandatory. |
| 400 | 997 | Cheque Date field must be in dd-MM-YYYY format. |
| 400 | 997 | Cheque Return Reason Code field is mandatory. |
| 400 | 997 | Value Date field is mandatory. |
| 400 | 997 | Value Date field must be in dd-MM-YYYY format. |
| 400 | 997 | OTB Release Date field is mandatory. |
| 400 | 997 | OTB Release Date field must be in dd-MM-YYYY format. |
| 500 | 999 | Invalid device number. |
| 500 | TRAN003 | Invalid Wallet number. |
| 500 | TRAN004 | Error while fetching Wallet details. |
| 500 | TRAN001 | Transaction notset in Transaction Plan. |
| 500 | TRAN002 | Transaction limit plan not attached. |
| 500 | TRAN005 | Transaction Reference number is mandatory in case of reversal. |
| 500 | TRAN006 | Cheque return reason is mandatory for Outstation cheque payment/cheque payment reversal. |
| 500 | TRAN007 | Invalid Cheque return reason. |
| 500 | TRAN011 | OTB release date should not be greater than transaction date. |
| 500 | PAY36 | Reversal already exists for Chq.No. |
| 500 | PAY37 | Original Record not found for Chq.No. |
| 500 | PAY38 | Error while saving details for Chq.No. |
| 500 | TRAN008 | Error while executing Transaction Payment API |
| 500 | TRAN020 | Invalid Transaction currency. |