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

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


---

# Agent Instructions: 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:

```
GET https://docs.ecwid.com/guides/payments/sample-payment-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.