> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/guides/payments/online-payments-overview.md).
# Online payments overview
Online payments in Ecwid stores always start with a customer going through the store checkout. At the last checkout step, a customer selects one of the available payment methods and clicks the “**Go to Payment**” button.
At this moment, the online payment processing flow starts:
Both storefront and backend processes happen at the same time.
During the first step, the customer is redirected to app's `paymentUrl` and at the same time the order data is sent to the same endpoint.
From there, the app handles both the storefront by redirecting customers to the payment page and back, and the backend by processing requests from Ecwid and callbacks from the payment provider.
---
# 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.ecwid.com/guides/payments/online-payments-overview.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.
