Appendix Error Codes
The table below contains the possible error codes & descriptions a merchant can expect to receive when making requests to our API. The below is intended to help build a superior system by handling any exceptions that may occur when integrating. Please note that these error codes are subject to change.
Error Code | Description | |||||
0 | Confirmation received | |||||
01 | 3D Confirm | |||||
100 | General Failure | |||||
101 | Invalid Username or Password | |||||
102 | Invalid APISignature | |||||
103 | Access API Denied | |||||
104 | Invalid Message ID | |||||
105 | Debit/Credit card transaction are not allowed | |||||
106 | Transaction Code already exists | |||||
107 | A Sale request with the sent transaction code is not present | |||||
108 | Authentication Error | |||||
109 | Not Enrolled | |||||
110 | Not Authenticated | |||||
112 | Transaction not executed | |||||
113 | Empth/Null data fields | |||||
114 | Message ID already exist | |||||
115 | Invalid date | |||||
116 | Incorrect date | |||||
117 | Currency cannot be process by Merchant | |||||
118 | Card Type cannot be process by Merchant | |||||
119 | Cannot Process ayn Transaction | |||||
120 | Invalid Fields | |||||
121 | Not found transaction | |||||
122 | 3D Verify failed |