Response Codes
The API Uses HTTP Status codes to communicate the result of a requested operation, the table below gives a list of status codes used.
Last updated
The API Uses HTTP Status codes to communicate the result of a requested operation, the table below gives a list of status codes used.
Last updated
200
OK - Action completed successfully
201
Created - create or update action completed successfully
204
No content - Delete or unlink action complete successfully
400
Bad request - Invalid or incomplete request parameters
401
Client needs to authorize with the authorization server and provide a valid access token
403
Forbidden - Client is not allowed to carry out requested action
404
Not found - The requested resource was not found
500
Internal server error
Find in the table below the response codes applicable to and their respective descriptions:
00
Approved or completed successfully
01
Status unknown, please wait for settlement report
03
Invalid Sender
05
Do not honor
06
Dormant Account
07
Invalid Account
08
Account Name Mismatch
09
Request processing in progress
12
Invalid transaction
13
Invalid Amount
14
Invalid Batch Number
15
Invalid Session or Record ID
16
Unknown Bank Code
17
Invalid Channel
18
Wrong Method Call
21
No action taken
25
Unable to locate record
26
Duplicate record
30
Format error
34
Suspected fraud
35
Contact sending bank
51
No sufficient funds
57
Transaction not permitted to sender
58
Transaction not permitted on channel
61
Transfer limit Exceeded
63
Security violation
65
Exceeds withdrawal frequency
68
Response received too late
69
Unsuccessful Account/Amount block
70
Unsuccessful Account/Amount unblock
71
Empty Mandate Reference Number
91
Beneficiary Bank not available
92
Routing error
94
Duplicate transaction
96
System malfunction
97
Timeout waiting for response from destination
F9
Unable to debit customer
-1
Transaction Pending
Client is not authorized to perform operations on this account
Client isn't logged in with accurate credentials
Confirm login credentials supplied by the bank, refresh page and try logging in again