Response Codes¶
Expected Response Codes¶
Below table is the list of expected response codes.
| Code | Type | Message |
|---|---|---|
000 |
Success | |
110 |
Error | Consumer not exist. |
111 |
Error | Transaction reference number is required. |
112 |
Error | Invalid subscribed date. |
113 |
Error | Invalid unsubscribed date. |
114 |
Error | Consumer already subscribed. |
120 |
Error | Invalid subscribed token. |
401 |
Error | Invalid authentication token. |
Expected Response Codes from Bank¶
Below table is the list of expected response codes from bank side.
| Code | Type | Message |
|---|---|---|
000 |
Success | |
301 |
Error | Insufficient funds or over credit limit. |
302 |
Error | The account has been blocked. |
303 |
Error | Duplicate transaction number. |
304 |
Error | The account is inactive. |
305 |
Error | The account was closed. |
306 |
Error | The account is invalid. |
307 |
Error | No subscription info found. |
308 |
Error | The subscription is already made payment for this month. |
309 |
Error | The subscription is over limit for payment for this month. |
310 |
Error | Company have disabled. |
311 |
Error | The settlement account was not found. |
312 |
Error | Payment was not success. |
313 |
Error | Transaction not found. |
313 – Transaction not found: OONE calls Payment Confirm to the bank, but the request does not reach the bank or fails due to an error, so the transaction is not created on the bank side. When OONE then calls Payment Verify for this transaction, the bank returns 313.
| 401 | Error | Invalid authentication token. |