> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/billing/details/payment-methods.md).

# Payment Methods

What we charge you with: credit card or SEPA direct debit, and how to change the active method.

In **Payment Methods** you define how we charge you.

The screen is a wizard, **Update payment method**, which guides you step by step depending on the method you choose.

There are two methods:

* **Credit card** — Visa, Mastercard, or American Express.
* **Bank direct debit** — SEPA direct debit from your account.

### Step 1: choose the method

Select **Credit card** or **Bank direct debit** and continue. From there, the data requested depends on the method.<br>

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-961662452378a4293291f955b60524abb6d4d884%2FPayment_methods_-_1.png?alt=media" alt=""><figcaption></figcaption></figure>

### Credit card

You enter the card information:

| Field        | What it is                                    |
| ------------ | --------------------------------------------- |
| Company name | The company that holds it.                    |
| Cardholder   | The name as it appears on the card.           |
| Card number  | The number, expiration date (MM/YY), and CVC. |

### Direct debit (SEPA)

Direct debit is completed in three steps: method, data, and mandate.

#### Account details

| Field          | What it is                          |
| -------------- | ----------------------------------- |
| Company name   | The company that owns the account.  |
| Account holder | The person or entity that holds it. |
| IBAN           | The account number.                 |

And contact and address details: email, mobile, country, province, postal code, city, and address.

> ❗️ Valid email and mobile
>
> To sign the mandate, we send an email and a 4-digit code by SMS. Make sure the email and mobile number are correct, or you won't be able to complete the process.

#### SEPA mandate

The last step is the **SEPA Core direct debit mandate**, with the creditor's and debtor's details and the type of payment (recurring or one-time). To finish, check the box **I authorize the direct debit mandate** and save.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-4fd8512d8257620edf2569bcadd5e08908066d81%2FPayment_methods_censored.png?alt=media" alt=""><figcaption></figcaption></figure>

### Your current method

If you already have a method set up, the screen shows it to you (for example, a direct debit with its company, holder, and IBAN) and offers you **Change payment method** to replace it.<br>

> 📘 Your tax details
>
> The tax details we use for billing (company name, holder, and address) are collected here, within the payment method setup.<br>

### Next steps

* Learn how to change it in [Add or change your payment method.](https://docs.plenit.com/docs-en/platform/billing/how-to/how-to-add-or-change-payment-method.md)
* Review how we bill you in [How we bill you.](https://docs.plenit.com/docs-en/platform/billing/concepts/how-we-bill-you.md)


---

# 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.plenit.com/docs-en/platform/billing/details/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.
