> 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/configurer-les-paiements-a-la-demande.md).

# Configure on-demand payments

### What are on-demand payments used for?

Some Yoplanning features are only charged when they are used.

To activate these features, you must register a bank card in your Yoplanning account.

Once your bank card is set up, payments are made automatically based on your usage. This allows you to use all services without interruption.

The main features concerned are:

* Purchasing SMS credits.
* Tokens for using artificial intelligence (AI) features.
* Technical committees related to connections with OTAs (Online Travel Agencies).

### How do I configure my bank card?

From the dashboard:

1. Open **Administration**.
2. Click on **Configuration**.
3. Open the **Yoplanning Billing** section.
4. Click on the **Manage** button, located in the top right corner.
5. Follow the steps to register your bank card.

Once the card is validated, your account is ready to use all features requiring on-demand payment.

### Best practices

#### Configure your card as soon as it is activated.

We recommend that you register a bank card as soon as you create your account. This will prevent any interruptions when using advanced features.

#### Check that your card is still valid

If your bank card expires or is replaced, remember to update it in the **Yoplanning Billing** section.

### Frequently Asked Questions

#### Why do I need to register a bank card?

Some features are charged based on your usage. A valid bank card is therefore required to use them.

#### Will I be charged immediately?

No. Registering your bank card simply authorizes payments for the services you use. Charges are only made based on your actual usage.

#### Can I use Yoplanning without a bank card?

Yes. Yoplanning's main features remain available. However, services that operate on a pay-as-you-go basis, such as SMS credits, AI features, or certain OTA connections, require a registered bank card.

### Common problems

#### The **Manage** button does not appear

Verify that you have administrative rights to the Team. If necessary, ask an administrator to perform the operation.

#### Unable to register bank card

Check the information you entered and make sure your card is authorized for online payments. If the problem persists, contact your bank or Yoplanning support.

#### A feature remains unavailable after saving the map

Check that the card has been successfully registered. If the problem persists after a few moments, contact Yoplanning support.


---

# 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/configurer-les-paiements-a-la-demande.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.
