> 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/test-cards-and-ach-accounts.md). # Test Cards & ACH Accounts To help you validate your integration, you can use the following test card and ACH account details to run transactions in the sandbox environment. {% hint style="warning" %} Don't use these test cards and ACH accounts in the production environment. {% endhint %} ### Test Cards

Card Type	Card Number	Expiration Date	Security Code	Billing Zip Code
Visa	4012 0000 9876 5439	MM/YY Any future date	999	85284
MasterCard	5499 7400 0000 0057	MM/YY Any future date	998	85284
MasterCard	2223 0000 4840 0011	MM/YY Any future date	998	85284
AMEX	3714 496353 92376	MM/YY Any future date	9997	85284
Discover (Use to test Surcharge Credit)	6011 0009 9302 6909	MM/YY Any future date	996	85284
Diners	3055 155515 1618	MM/YY Any future date	996	85284
JCB	3530 1420 1994 5859	MM/YY Any future date	996	85284

### ACH Test Account {% hint style="warning" %} Don't use these numbers for ACH test transactions over $25. {% endhint %}

Routing Number	Account Number
490000018	Any digits

--- # 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/test-cards-and-ach-accounts.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.