> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/web-view/web-view-checkout.md).

# Web view checkout

### Why is my WooCommerce app redirected to a web view checkout?

AppMySite is designed to support any payment gateway that you use on your WooCommerce website, regardless of the provider or region. This ensures seamless transactions for your customers, no matter where they are.

### **How payment gateways work in your app**

* **Web View Checkout Integration**
  * When customers proceed to payment in the app, they are redirected to a Web View interface that mirrors your website’s checkout page.
  * This ensures that your app maintains full compatibility with all payment gateways, including third-party and region-specific options.
  * All discount coupons and custom rules set up on your website will automatically work in the app checkout. No additional setup is needed.

{% hint style="success" %}
Since payments are processed via Web View, any updates made to the payment gateway on your website will automatically reflect in the app—no extra configuration required.
{% endhint %}

* **Universal payment gateway support**
  * Whether you're using Stripe, PayPal, Razorpay, Square, or any local provider, your customers can complete transactions just as they would on your website.

{% hint style="success" %}
There are no restrictions on which payment provider you use—if it works on your WooCommerce website, it will work in your app.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/app/web-view/web-view-checkout.md?ask=<question>&goal=<user_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.