Breaking changes

Updates computation of subscription schedule phase end date to consider billing cycle anchor changes Breaking changes

What’s new

Adds consideration of any billing_cycle_anchor changes to the end_date calculation when you create a subscription schedule without explicitly setting a phase’s end_date. That aligns the end_date more closely with the subscription’s billing cycle. Previously, the calculation only used the interval, interval_count and the previous phase’s end_date.

Why is this a breaking change?

If your integration depends on the automatically calculated value of a phase end_date, a calculated end_date might differ from the values you expect based on the previous formula.

Impact

A subscription schedule’s computed phase end_date now aligns more closely with the billing cycle. This change applies only to new subscription schedules and doesn’t affect existing schedules.

Upgrade

1. View your current API version in Workbench.
2. If you use an SDK, upgrade to the corresponding SDK version for this API version.

• If you don’t use an SDK, update your API requests to include Stripe-Version: 2025-09-30. clover

3. Upgrade the API version used for webhook endpoints .
4. Test your integration against the new version.
5. If you use Connect, test your Connect integration .

Learn more about Stripe API upgrades.

Related changes

• Removes iterations parameter for subscription schedules
• Promotion Codes now reference Coupons using a polymorphic field for promotions
• Adds the Discount source property and removes the Discount coupon property
• Makes flexible billing mode the default for new subscriptions
• Adds customer portal configuration trial behaviour
• Adds the ability to itemise proration discount amounts