Errors Guide

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 directly from TabaPay to indicate the status of a request, or transaction.

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.

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.
  • ERROR: Transaction processing error. Means the issuer actively declined the transaction.

Note: UNKOWN doesn't necessarily mean an error, refer to Transaction Result is Unkown

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.

Response Code Errors

Response Code Errors are errors from networks or TabaPay to indicate select reasoning or failures.

Card Network Response Code Errors

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

Other Network Errors
Match/Reason Codes

Network Outages

Unexpected outages may temporarily affect transaction processing (e.g. Response Code: 91). While investigating transaction errors, check the following system status page to determine whether a service disruption has been reported.

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.


Did this page help you?