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.

Routing and Permission Errors

Routing and permission errors may occur when a request uses an incorrect ClientID or SubClientID, a feature is not enabled, or the transaction is routed to an unsupported payment network.

Error	Possible Cause	Action Required
`400` / `EM: authorize`	Authorization and Capture is not enabled, or the transaction is routed to a network that does not support the requested authorization flow.	Confirm the ClientID, SubClientID, and network configuration to ensure Auth & Capture is enabled.
`403` / `EM: Permission`	The Client or SubClient does not have permission to use the requested API operation or feature.	Confirm each unique ID, environment variables, and features enabled on the Client or SubClienID.
Connection failure or gateway `403`	The request may originate from an IP address that is not allowlisted.	Confirm the source IP address is enabled for the correct Sandbox or Production environment.
`500`	A server or processing error occurred.	Review the response and transaction status before retrying. Contact TabaPay Support if the issue persists.

Check Your Routing Configuration

ClientID: Confirm the request uses the correct ClientID for Sandbox or Production.
SubClientID: Confirm the correct SubClientID is included for supported SubClient-level transactions. For more info, refer to Send API Requests for a SubClientID
Network Routing: Verify that the SubClient is configured for the requested card network and transaction type.
Single or Dual Message: Confirm that the network supports the requested authorization and capture flow.
Permissions: Confirm that the API operation and payment feature are enabled for your Client.

Contact TabaPay Support

If the issue persists, contact TabaPay Support with:

Client Name and ClientID
SubClientID, if applicable
Environment (Sandbox or Production)
API endpoint and HTTP method
Sanitized API request and response, including SC, EC, and EM
Source public IP address, if investigating an access issue

Do not include full card numbers, CVV/CVC values, API credentials, or other sensitive payment information.

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

See errors for other networks

Match/Reason Codes

See errors for different Risk & Fraud tools:

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.