6. Handling of Response Codes
Following are the list of response codes used in NPI that could be technical and business. HTTP Reason codes FORBIDDEN, BAD REQUEST and INTERNAL SERVER ERROR are exceptional cases which requires the exact technical setups and message structures mentioned in the document. These HTTP statuses contain same response message format as mentioned below with response code. All technically valid messages will be responded with HTTP status OK which has a fixed format and doesn’t change.
Technical Response Format (FORBIDDEN, BAD REQUEST and INTERNAL SERVER ERROR):
{
"responseCode":”<Response Code>",
"responseDescription":"<Response Message>",
"fieldErrors":[<Field Error if any>]
}
Response Codes:
| Technical Error Codes | ||
|---|---|---|
| HTTP Status | Error Code | Error Description |
| HttpStatus.FORBIDDEN | E001 | INVALID IP ADDRESS |
| HttpStatus.BAD_REQUEST | E007 | TECHNICAL VALIDATION FAILED (Batch and Txn Level) |
| HttpStatus.BAD_REQUEST | E003 | INVALID TOKEN |
| HttpStatus.BAD_REQUEST | E004 | INVALID ACCOUNT |
| HttpStatus.BAD_REQUEST | 99 | DUPLICATE BATCH TRANSACTION |
| HttpStatus.INTERNAL_SERVER_ERROR | E999 | ERROR |
| Https Status | 200 OK | Success |
| Https Status | 200 OK | E021 Transaction Time Out |
| Business Validations Codes | ||
|---|---|---|
| Debit Response | ||
| Response Code | Description | |
| 000 | Debit Success | |
| 1001 | Bank network not reachable | |
| 999 | Debit ISO Time Out | |
| 1000 | Debit rejected | |
| ENTR | Debit in Progress | |
| Credit Response (POSTCIPS) | ||
| 000 | Credit Success | |
| 1001 | Bank network not reachable | |
| 1000 | Credit Rejected as Debit is Rejected | |
| 999 | Credit ISO Time Out | |
| DEFER | Deferred Credit Payment/Success | |
| ENTR | Credit in Progress | |
| Credit Response (POSTNCHLIPS) | ||
| ACTC | Accepted Technical Validation | |
| ACSP | Accepted Settlement in Process | |
| ACSC | Accepted Settlement Completed | |
| RJCT | Credit Rejected | |