There are several types of errors you may receive when using the TabaPay API. The following will guide you through your investigation to resolve your case. For help, contact Support, or email [email protected].

API Response Errors

API Response Errors are errors from networks, transaction status, or the API directly to indicate the status of a request.

HTTP Status Code Errors

HTTP Status Codes (SC) Errors are returned from interacting with the TabaPay's API. SCs are are returned in compact JSON format like the following {"SC":200...}

200 or 201 are successful returns, however other SCs returned will indicate what type of error may have occurred.

Network Response Code Errors

Network Response Codes (RC) Errors are returned from the network after sending the Create Transaction API request.

Transaction Resource Status Errors

Transaction Resource Status indicates the current status of a requested transaction. The following errors are listed for Create Transaction:

Failed: Transaction processing failed. Unknown: Transaction processing result is unknown. Indicates that there was an issue downstream and no response was received from the issuer.
Failed: Transaction processing error. Means the issuer actively declined the transaction.

For all transaction resource status, be sure to check the Network Resource Codes (RC) to learn how to follow up, or take action.

Error Messages

Error Messages help direct clients to troubleshoot the current error by indicating what might be wrong. PCI does require TabaPay to be cryptic in the Error Messages that are returned back.

Errors Returned in Reports

There are certain errors that will only show up in reports due to the nature of the payment and network. These errors will show up in the Exceptions Report in the Exceptions Code column.

RPPS Exceptions Codes

RPPS Exception Codes are sent in the Exceptions report, and include errors for failed RPPS payments.

ACH Return Codes

ACH Return Codes are sent in the Exceptions report, and include errors for failed ACH payments.