> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/v.9-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/v.9-documentation/user-guide/improving-shop/managing-payments/payment-methods.md).

# Payment Methods

The "Payment Methods" page is pretty straightforward, with two sections.

**Active payment**. The payment methods currently enabled on your shop. An action button allows you to manage the modules, with the same options that the ones available on the Modules page.

**Recommended payment gateways**. Depending on your location and shop settings, PrestaShop will show you the available payment methods for your country or the markets you are targeting. You can then choose to add payment methods that are relevant to your customers' expectations. Some modules can be installed for free, while others are paying. In that case, you will be redirected to Addons, to buy the module, before you can install it.

## Installing a Payment Module <a href="#paymentmethods-installingapaymentmodule" id="paymentmethods-installingapaymentmodule"></a>

Installing a payment module is fundamentally no different from installing a regular module: simply click the "Install" button, and all that is left to do is to configure the module.\
You should pay a lot of attention to the settings, and make sure they do point to your address or bank account. Configuring payment modules often means you must first be known by the payment service provider, meaning having an account on their service.

Video - 4 ways to improve conversion with payments

[![](https://content.gitbook.com/content/f4jUT8dUfW1PrFTeHOkK/blobs/wBpI6hY9GOK2woIiclUH/51839799%20\(7\)%20\(7\).png)](https://www.youtube.com/watch?v=i_wwnGt7JKM\&list=PLyZYn1MMU7-xT-L_zUyGnRBJmAuP6uc-c\&index=19)


---

# 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.prestashop-project.org/v.9-documentation/user-guide/improving-shop/managing-payments/payment-methods.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.
