> 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-request-validation-codes.md). # ACH Request Validation Codes We will validate your ACH request utilizing the following rules to help reduce returned ACH payments. Below are common validations for the incoming request on ACH transactions.


	Amount must include two decimal places
	Amount must only contain digits and a decimal point
	Amount must be 0.00 for validate transaction
	Amount required (absolute number with two decimal places)
	Routing number required
	Account number required
	Individual name required
	Account type required (`Checking` or `Savings`)
	Routing number should be 9 digits
10.	Account number should be 1 to 17 digits
11.	Transaction-key should not be provided
12.	Valid values are `true` or `false`
13.	Type should be `Debit` — Transfer funds from the customer bank account to your (merchant) bank account or `Credit` — Transfer funds from your (merchant) bank account to customer bank account
14.	Software type required. Please provide the name of your software, product, or service
15.	Software type version required. Provide version of software-type
16.	Provider `Account Id` required
17.	Valid values are `Pending`, `Settling`, `Returned`, or `Settled`
18.	Invoice value required if invoice is the check-field

--- # 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-request-validation-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.