# Payment Plans (Subscription Schedules)

There are several uses for the Payment Plan or split payments Pricing model. The first is to break a large one-time payment into several monthly payment to increase sales of a given product. The second is to create an automatically cancelling subscription that behaves like a paid trial of a service. The setup for both of those scenarios is the same and we start by creating a Product in Stripe.

![](/files/-MJ3Owp9tWG8u5RH_J-s)

You will configure a Recurring product so that the customer is charged on the given billing interval. You can set the Billing period to any interval you need, and monthly is most common.

![](/files/-MJ8L2EpCGDwrm98UEBR)

Now that we are done creating the products, for Billflow to recognize these products as a single service we need to tag it with an "sb\_service" tag. This tag should be the same for all products(pricing plans) that are in the model. Next we tag each with a unique "sb\_tier" that corresponds to the plan. That means we have 2 unique "sb\_tier" tags for our example. \
Specifically for Payment Plans, we need to add a third metadata value and that is "sb\_plan\_iterations". Set this to the number of times the customer should be charged. For example, if you want the customer to pay $600 in 6 monthly $100 payments, the value of "sb\_plan\_iterations" would be 6. After 6 months, the subscription will automatically cancel.

![](/files/-MYM4bEYCjCP22BTsj4Y)

Finally, we go back to Billflow and refresh the "Pricing Plan" page. We should see our pricing plan pop up. 

![](/files/-MYM4tvDnQrShv8L4CpE)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.billflow.io/how-to/setup-pricing/payment-plans-subscription-schedules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.