Overview
This API returns details of cheque book received most recently, basis accountNum and start/end date.
Response field Status indicates the status of the cheque book request. For status inquiry, it will return code as follows:
| Code | Code Description |
|---|---|
| 000 | Financial transaction has been approved (DCC should go ahead and complete the transaction) |
| 111 | Invalid scheme type |
| 114 | Invalid account number (DCC should reject the transaction) |
| 115 | Requested function not supported (First two digits of processing code or Function code is invalid) (DCC should reject the transaction) |
| 116 | Insufficient funds (DCC should reject the transaction) |
| 119 | Transaction not permitted to card holder (DCC should reject the transaction) |
| 121 | Withdrawal amount limit exceeded. (DCC should reject the transaction) |
| 163 | Invalid Cheque Status |
| 180 | Transfer Limit Exceeded (DCC should reject the transaction) |
| 181 | Cheques are in different books |
| 182 | Not all cheques could be stopped |
| 183 | Cheque not issued to this account |
| 184 | Requested Block operation failed since Account is closed/frozen. Account status is sent in ISO field 125. Note that brokerage requests can be processed on a Credit freeze account and not permitted on Total Freeze/Debit freeze/Closed Accounts. |
| 185 | Invalid Currency/Transaction Amount |
| 186 | Block does not exist |
| 187 | Cheque Stopped |
| 188 | Invalid Rate Currency Combination |
| 189 | Cheque Book Already Issued |
| 190 | DD Already Paid |
| 800 | Network message was accepted |
| 902 | Invalid transaction (Invalid function code within network management messages) (DCC should reject the transaction) |
| 904 | Format Error (Any format related errors etc) (DCC should reject the transaction) |
| 906 | Cut-over in progress (When Stand-in Server is handing over control to FiNACLE. (DCC should reject the transaction and try again after some time or do local authorization) |
| 907 | Card issuer inoperative (When BancsConnect cannot contact FiNACLE and cannot do stand-in processing.) (DCC should reject transaction and do local authorization ) |
| 909 | System malfunction (Sent by BancsConnect for errors like database corrupted) (DCC should reject transaction and do local authorization) |
| 911 | Card issuer timed out (BancsConnect contacts FiNACLE and FiNACLE times out and 24 Specification for AXIS_ESBService Integration with Enterprise Service Bus BancsConnect cannot do stand-in processing) (DCC should mark transaction as ‘suspect’ and do local authorization ) |
| 913 | Duplicate transmission. This error is returned if a duplicate message is received and the transaction amount is different. The DCC will have to treat this transaction as ‘suspect’ and carry out the necessary steps to process suspect transactions. |
Type
REST
OAS2
Protocol
HTTPS
Endpoints
Production, Development:
https://apiportal.axisbank.com/gateway/v2/JSON/C24
Production, Development:
https://apiportal.axisbank.com/gateway/axis/esb
Security
clientIdHeader
X-IBM-Client-Id
apiKey located in header
clientSecret
X-IBM-Client-Secret
apiKey located in header
Focus sentinelFocus sentinel
