> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/memberships/managing-memberships/letting-members-pay-for-a-membership-in-installments.md).

# Letting Members pay for a Membership in installments

### Overview

The system does not have a native installment feature for Memberships. A Club can still split a Membership charge into installments by giving each Customer a custom rate and moving their Next Charge Date by hand after each payment.

The process is manual and repeats for every installment, so it works best when the Club picks a small set of shared installment months for all Customers paying this way.

{% hint style="warning" %}
**Installments are not a supported Membership option.** PodPlay does not track the installments, send reminders, or move the Next Charge Date for you. Each step below is a manual change the Club makes in the Dashboard, and a missed step means a missed or incorrect charge.
{% endhint %}

### Before you start

1. Make a list of every Customer paying for their Membership in installments
2. Record each Customer's installment amount and current Next Charge Date
3. Choose the months the installments will be charged (for example, November, January, and March) and use the same months for every Customer on the list

Using shared installment months lets you update every Customer on the list in one pass each cycle instead of tracking a separate schedule per Customer.

### Setting up and running the installments

The example below uses a $900 Membership split into three $300 installments, for a Customer whose Next Charge Date is November 2.

#### First installment

At the end of the month before the first installment, or at the start of that month:

1. Open the Customer's Profile in the Dashboard
2. Set a custom rate of `$300` on their Membership
3. Confirm the Next Charge Date is in the first installment month (November 2 in this example)
4. Repeat for every Customer on the list

#### Second installment

After the first installment charges (end of November or start of December):

1. Change each Customer's Next Charge Date to the second installment month (January 2 in this example)
2. Leave the custom rate at `$300`

#### Third installment

After the second installment charges (end of January or start of February):

1. Change each Customer's Next Charge Date to the third installment month (March 2 in this example)
2. Leave the custom rate at `$300`

#### After the final installment

Once every installment is paid:

1. Change each Customer's Next Charge Date back to their original renewal month (November 2 in this example)

{% hint style="info" %}
**The Next Grant Date moves independently of the Next Charge Date.** Changing the Next Charge Date does not change when a Customer's Membership benefits or Package are granted. Check the Next Grant Date if a Customer reports missing benefits during the installment period.
{% endhint %}

### Verify it worked

* Each Customer on the list shows the installment amount as their custom rate.
* Each Customer's Next Charge Date matches the next installment month.
* After each installment month, the Customer's payment history shows one charge for the installment amount.


---

# 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.podplay.app/memberships/managing-memberships/letting-members-pay-for-a-membership-in-installments.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.
