Subscription Schedules API
You can now model subscriptions more flexibly using the Prices API. It replaces the Plans API and is backward compatible to simplify your migration. If you’re new to Stripe, learn how to create products and prices. If you already use the Plans API, learn how to update your integration.
Subscription schedules are used to automate changes to subscriptions over time. You can create subscriptions directly through a schedule or you can add a schedule to an existing subscription. Use the phases attribute to define the changes you want to make to the subscription. After a schedule completes all of its phases, it completes based on its end_behavior.
Some changes you might want to schedule include:
- Starting a subscription on a future date
- Backdating a subscription to a past date
- Upgrading or downgrading a subscription
The rest of this document explains subscription schedules in more detail. To see a list of examples, see the use cases page.
Phases
When creating a subscription schedule, use the phases attribute to define when changes occur and what properties of the subscription to change. For example, you might offer a coupon for 50% off for the first three months of a subscription. In this scenario, you’d create a subscription schedule where the first phase is three months long and contains the 50% off coupon. In the second phase, the subscription would be reverted to the normal cost and the coupon would be removed. Phases must be sequential, meaning only one phase can be active at a given time.
Setting the length of a phase
The interval of a price determines how often to bill for a subscription. For example, a monthly interval is billed every month. Phases have an iterations attribute that you use to specify how long a phase should last. Multiply this value by the interval to determine the length of the phase. If a subscription schedule uses a price with a monthly interval and you set iterations=2, the phase lasts for two months.
The end_date of one phase has to be the start_date for the next phase. Using iterations automatically sets the start_date and end_date properly. You can set these values manually, but Stripe recommends using iterations instead. Because manually setting the start and end dates is prone to errors, only use it for advanced use cases.
Transitioning to the next phase
Phase transitions happen automatically after the end_date on a phase is reached. When a phase starts, Stripe updates the subscription based on the attributes of the next phase. You can optionally enable proration to credit the user for unused items or time on the plan.
Using trials
You can add trial periods by setting trial end on a phase. If you want the entire phase to be a trial, set the value of trial_end to the same time as the end_date of the phase. You can also set trial_end to a time before the end_date if you want to make only part of the phase a trial. When scheduling updates, you must specify the new trial_end on each phase.
Completing a schedule
Subscription schedules end after the last phase is complete. At this point, the subscription is left in place and is no longer associated with the schedule. If you want to cancel a subscription after the last phase of a schedule completes, you can set end_behavior to cancel.
Phase attribute inheritance
When a phase becomes active, all attributes set on the phase are also set on the subscription. After the phase ends, attributes remain the same unless the next phase modifies them, or if the schedule has no default setting. You can set some attributes on both schedules and phases. This includes:
If one of these attributes is defined on the schedule, it becomes the default for all phases. When the same property is defined on both the schedule and the phase, the phase attribute overrides the schedule attribute. This behavior is explained more below:
| Schedule attribute present | Phase attribute present | Outcome |
|---|---|---|
| No | No | Defaults to the customer or account settings |
| Yes | No | Schedule attribute set |
| Yes | Yes | Phase attribute set |
| No | Yes | Phase attribute set |
Creating subscription schedules
The use cases page has more thorough examples but below is a basic example of creating a subscription schedule using a customer. Creating a schedule this way automatically creates the subscription as well.
This schedule:
- Starts as soon as it’s created.
- Sets the subscription to one instance of the product at
price_1GqNdGAJVYItwOKqEHb. - Goes through 12 iterations and then releases the subscription from the schedule.
You can also create subscription schedules by passing a subscription ID:
Creating a schedule this way uses attributes on the subscription to set attributes on the schedule.
Similar to other Stripe APIs, you can retrieve and update subscription schedules. You can also cancel and release them. Cancelling a subscription schedule cancels the subscription as well. If you only want to remove a schedule from a subscription, use the release call.
Updating subscription schedules
You can only update the current and future phases on subscription schedules. When updating a subscription schedule, you need to pass in all current and future phases that you want to keep. You still receive information in the response about past phases.
Updating the active phase updates the underlying subscription as well. For example, this call maintains the existing start and end dates, but updates the quantity to two:
You can also end the current phase immediately and start a new phase. This moves the active phase to the past and immediately applies the new phase to the subscription. The example below ends the current phase and starts a new phase:
To add additional phases to a subscription schedule, pass in the current phase, and then define your new phases: