> For the complete documentation index, see [llms.txt](https://docs.codemash.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codemash.io/dashboard/payments/integrations/paysera.md).

# Paysera

{% hint style="info" %}
This documentation is a work in progress, and we welcome your feedback and suggestions. Please let us know if you have any questions or if there is anything else you would like to see included in the documentation.
{% endhint %}

Paysera is a payment gateway that allows businesses to accept payments online. It provides various tools and features to help businesses manage their payments and subscriptions, including support for multiple currencies, customizable checkout pages, and fraud protection.

To use Paysera, businesses must first create an account and connect it to their website or app. Once the account is set up, businesses can start accepting payments from their customers by creating payment buttons or forms on their website or integrating Paysera into their app.

Paysera supports various payment methods, including credit and debit cards, mobile payments, and online bank transfers. It also offers support for multiple languages and countries, making it a convenient option for businesses with a global customer base.


---

# 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.codemash.io/dashboard/payments/integrations/paysera.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.
