When a Wrapper API request (Publish, Status or Cancel) can't be processed, the API returns an Error Code and an Error Message in the response. The table below explains when each error occurs. Use the Error Code in your integration logic, and for timeouts or in-progress transactions, check the transaction status before sending a new request.
| Error Code | Error Message | Error Description |
|---|---|---|
| VC01 | CHANNEL ID REQUIRED | Channel ID property is required. |
| VC02 | PAYLOAD REQUIRED | Required payload must be provided properly. |
| VC03 | DEVICE OFFLINE | Returned when the POS terminal is not in listening mode. |
| VC04 | TRANSACTION TEMPORARILY UNAVAILABLE DUE TO CONNECTIVITY ISSUES. PLEASE TRY AGAIN SHORTLY | Occurs when the Wrapper API is down (Publish API or Status API). |
| VC05 | TRANSACTION IS ALREADY IN A PROCESSING STATE | When a transaction request is sent, the corresponding EPI is blocked in the Wrapper API for up to 3 minutes or until the initiated transaction completes. Sending another request for the same EPI during this time will result in this error (Publish API). |
| VC06 | REQUEST TXN ID REQUIRED | The REQ_TXN_ID field is missing in the request. |
| VC07 | TRANSACTION TIMEOUT, USE TRANSACTION API TO FETCH STATUS | This usually occurs when activity at the terminal exceeds 120 seconds, such as manual card entry taking longer than expected. The transaction continues at the terminal instead of being cancelled. |
| VC08 | TRANSACTION INPROGRESS | Returned by the Status API when the requested transaction is still in progress. |
| VC09 | UNABLE TO FETCH TRANSACTION STATUS | Returned when the requested transaction ID (REQ_TXN_ID) does not exist (Status API). |
| VC10 | REQUEST TXN ID ALREADY EXIST | Returned when the requested transaction ID (REQ_TXN_ID) is already used. |
| VC11 | SEND A VALID PAYLOAD | The payload is not a valid JSON object. |
| VC12 | UNABLE TO CANCEL TRANSACTION RIGHT NOW | Returned when the Cancel API is not available or not functioning (Cancel API). |
| VC13 | NOT A VALID ISV CLIENT | The ISV key is not valid for this merchant. |
| VC14 | MERCHANT IS NOT ASSOCIATED WITH THIS ISV | The merchant is not associated with this ISV. |
Showing 14 of 14 entries