Transaction Processing API Error Numbers and Descriptions

Created by Richard Moore, Modified on Wed, 28 Feb 2024 at 10:38 AM by Anna Byazina

The error number and description values sent in the response indicate the status of how a request was handled by the Transaction Processing API. The error number value “0” indicates that no error occurred while handing the request. A non “0” value indicates that an error occurred.


The error values may be passed back through the “detail” element of a Soap Exception or in the response properties Error_Number and Error_Description. The possible error values are defined in the table below.


If a Code Element has a “Client” value, this indicates that the incoming message was incorrectly formed or did not contain the appropriate information in order to succeed. It is a general indication that the message should not be resent without change.


If a Code Element has a “Server” value, this indicates that the incoming message could not be processed for reasons not directly attributable to the contents of the message itself but rather to the processing of the message. The same message may succeed at a later point in time.



Code ElementError NumberError Description
 0/200No error occurred. No details returned.
Client400Bad Request. Additional details.
Client401Unauthorized. Additional details.
Client402Payment Required. Additional details.
Client403Forbidden. Additional details.
Client404Not Found. Additional details.
Client405Method Not Allowed. Additional details.
Client406Not Acceptable. Additional details.
Client407Proxy Authentication Required. Additional details.
Client408Request Timeout. Additional details.
Client409Conflict. Additional details.
Client410Gone. Additional details.
Client411Length Required. Additional details.
Client412Precondition Failed. Additional details.
Client413Request Entity Too Large. Additional details.
Client414Request-URI Too Long. Additional details.
Client415Unsupported Media Type. Additional details.
Client416Requested Range Not Suitable. Additional details.
Client417Expectation Failed. Additional details.
Server500Internal Server Error. Additional details.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article