> For the complete documentation index, see [llms.txt](https://api.veratad.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.veratad.com/testing.md). # Testing ## How does testing work? Each Veratad service comes with a target attribute called `test_key`. This attribute tells the system that the transaction is for testing purposes. Once the system knows that it is a test it will drop the live data and other verification sources and use a fake database with known data values. ## Do I need to change my endpoint? No. The endpoint, service name and user credentials all stay the same when testing. ## Is testing free? Yes. Whenever the `test_key` attribute is sent with a valid value then those transactions are not billable. {% hint style="danger" %} It is important to follow the testing instructions when integrating. Transactions that are not sent as test are billable to your company. {% endhint %} ## Do services have different test cases and methods? Yes. Check your specific service documentation for exact testing instructions. In some cases the responses are canned, and so, regardless of input you will receive a known response. This is not true of all services, and so, in some cases when you send the key the system will run it through the normal verification checks so you can manipulate responses based on your target inputs. ## Are there any services that I am unable to test? Yes. Services like PhoneMatch5.0.SMS where you need to send an OTP to a real phone is impossible to test without using the live service. Please consult with your Veratad representative on this as they will allot you a certain amount of free live transactions for testing. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://api.veratad.com/testing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.