> 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/sample-payment-app.md).

# Sample payment app

[Sample payment app](https://github.com/Ecwid/payment-gateway-template) contains several files covering its essential features:

* **payment-request.php** file contains the code for decoding and processing payment requests from Ecwid stores. Essentially, it’s your `paymentUrl` endpoint. Every time a customer clicks the “Go to Payment” button at the checkout, Ecwid sends a new payment request that the `paymentUrl` must process.
* **index.html** (optional) file provides a user settings page for the app. Store owners can access this page in Ecwid admin and fill in their settings, like API keys or account credentials required for connecting the payment gateway.
* **functions.js** (optional) file that allows saving user settings in the App Storage hosted on Ecwid side. Only used with **index.html**.

{% hint style="info" %}
If you build an integration for one store, then you can simplify the process even more by only using the **payment-request.php** file. \
\
Any credentials and other variables for connecting the payment gateway can be added to the file.
{% endhint %}

The sample app is hosted on GitHub.&#x20;

[**Go to GitHub to get the code**](https://github.com/Ecwid/payment-gateway-template)


---

# 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/sample-payment-app.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.
