> 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-au-quotidien/manipulation-et-gestion-des-commandes-dans-yoplanning/utiliser-le-credit-ou-le-forfait-prepaye-dun-client.md).

# Using a Customer's Credit or Prepaid Package

#### Introduction

If your client has a voucher, voucher booklet, credit, or prepaid plan on the Yoplanning.pro app, you can use it to pay for an order. In this article, we explain how to use these vouchers directly in the schedule or from the booking module.

#### Using Credit in Yoplanning

1. Create an order with the services in the usual way.
2. When you get to the payment stage, you will see a link under the "Add a payment" button: **"Use a voucher"**.
3. Click on the link and enter the **voucher code**, or the name of the customer who holds the credit. Note that you can use credit from a different customer than the one who placed the order.
4. Enter the desired amount of credit to use, then click "Save". The customer's credit amount will then be deducted to pay for the order.

#### Using Credit from the Booking Module

1. On the customer's ticket, you will find a code in the top right corner. This code allows you to validate the voucher in your booking system.
2. In the final step of the shopping cart, at the time of payment, there is a field to enter the voucher code.
3. The customer can then enter the code to use their credit directly online. The credit amount will be deducted from the order total.

#### Case of the voucher book

A [voucher booklet](file:///yoplanning-academie/yoplanning-parametrage/parametrage-produit/les-forfaits-prepayes-bons-cadeaux-cheques-cadeaux/carnet-de-bons.md) is entered in the same way, with some differences in behavior:

* the logbook records **uses**, not euros: there is no amount to enter;
* A single entry of the code can cover **multiple participants in the same order**, within the limit of remaining uses;
* The **book price replaces** the session price, including a sliding scale price;
* the same code cannot be entered **twice on the same order**;
* If the order is cancelled, the uses are **returned** to the notebook.

The remaining usage counter can be viewed in the **Vouchers** menu ("Remaining: 7 / 10").

***

In short, Yoplanning.pro's voucher, booklet, credit, and prepaid package system offers great flexibility for managing payments, whether directly within the schedule or from the booking module. If you encounter any problems using these features, please don't hesitate to contact our support team for assistance.


---

# 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-au-quotidien/manipulation-et-gestion-des-commandes-dans-yoplanning/utiliser-le-credit-ou-le-forfait-prepaye-dun-client.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.