> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-webstore/steps-to-launch-your-web-store/step-4-production-test-with-coda.md).

# Step 4: Production Test with Coda

Once the production release has been completed; Coda’s integration team will request a production test ID from the publisher. Coda's QA team will arrange for end-to-end testing to simulate the customer’s purchase experience on your web shop.

This includes entering the User ID on your webstore to complete the payment process and receiving an official confirmation email. This test is used to test the purchase flow and whether the purchased item has been credited to the user's account. Testing transaction ID will then be shared with the publisher's integration team to verify.

{% hint style="info" %}
Note: A push notification in the app is ideal to inform customers of their top-up from your webstore.
{% endhint %}


---

# 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://docs.coda.co/coda-webstore/steps-to-launch-your-web-store/step-4-production-test-with-coda.md?ask=<question>&goal=<endgoal>
```

`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.