> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-general-de-yoplanning/liste-des-modes-de-reglements.md).

# List of payment methods

## **Introduction to Payment Methods**

Before starting, it is essential to remember that the choice of a payment method must reflect the reality of your activity. Avoid using irrelevant elements as a payment method (for example, the name of a company). The means of payment must correspond to real methods such as bank card, cash, check or transfer, holiday voucher, credit card, etc.

## **Addition or Modification of Payment Methods**

1. **Access the Configuration Section:**
   * In the left menu, select **Administration**.
   * Then go to **Configuration**.
2. **Navigate to Payment Methods:**
   * In the **Sales** section, click on **Payment Methods**.
3. **Manage Payment Methods:**
   * You arrive on the payment methods management page.
   * To add a new payment method, enter it as a simple string. For example, enter **"Cash"**.
   * After entering, click **Save** to add the payment method to your list.

**User Tips and Best Practices**

* **Clarity and Precision:** Make sure each payment method is clearly defined and easily recognizable to avoid confusion during transactions.


---

# 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.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-general-de-yoplanning/liste-des-modes-de-reglements.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.