> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/api-reference/resources/ach-request-validation-response-and-return-codes/ach-response-codes.md). # ACH Response Codes ACH response codes indicate the status of your ACH transaction requests. The following table lists all ACH response codes, their corresponding HTTP status codes, and error messages:

Error Type	Result Code	HTTP Status Code	Error Message
TRANSACTION_ERROR	280	400	Transaction failed
VOID_ERROR	281	400	Void failed. Cannot void ach transactions that are returned or settled.
VOID_ERROR_CANNOT_FIND_STORED_ACCOUNT_INFO	281	400	Void failed. Cannot find account info
AUTHORIZATION_ERROR	282	400	Authorization failed
ACCOUNT_VALIDATION_ERROR	283	400	Validation failed
ACCOUNT_NOT_CONFIGURED_ERROR	284	400	ACH Account not found
ACCOUNT_DISABLED_ERROR	285	400	ACH Account is disabled
ACCOUNT_DISABLED_FOR_SECCODE	285	400	ACH Account disabled for Sec Code
UNACCOUNTED_ERROR	286	400	An error occurred we did not account for
TRANSACTION_NOT_FOUND	287	404	Transaction not found
REQUEST_FAILED	288	400	Request failed
PROVIDER_ERROR	289	400	Provider failed
QUEUE_ERROR	290	500	Transaction Failed
PROVIDER_INTERNAL_ERROR	291	400	Ach Provider returned an internal error.
SETTLED_DATA_EMPTY	292	404	Transaction not found
RETURNED_DATA_EMPTY	293	404	Transaction not found
PROVIDER_SERVICE_UNAVAILABLE	294	500	Ach Provider service is unavailable.
ACH_TRANSACTION_WAREHOUSE_SERVICE_UNAVAILABLE	295	500	Clearent Ach Warehouse service is unavailable.
ACH_TOKEN_DECRYPTION_ERROR	296	400	Unable to decrypt token.
ACH_TOKEN_LOOKUP_ERROR	296	400	Unable to query token data
INVALID_REQUEST	074	400	First Name Required The following characters are not allowed in the first name field: `', +, (, ), ` This restriction is enforced by PAYA.*
GET_NOT_FOUND	082	404	Merchant configuration not found
PAYA_ACCOUNT_NOT_FOUND	082	404	Paya account not found
NO_BODY_IN_REQUEST_088	088	400	No body in request
FAILED_TO_PROCESS_HPP_REQUEST	880	400	Failed to process hpp request.
UNAUTHORIZED	042	401	Unauthorized
SYSTEM_ERROR_OTHER_073	073	500	System Error Other

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xplorpay.com/api-reference/resources/ach-request-validation-response-and-return-codes/ach-response-codes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.