Setting the subscription billing cycle date

A subscription’s billing cycle depends on two factors:

• The recurring interval of its price or prices, such as monthly, yearly, weekly, and so on.
• The billing cycle anchor is the reference point that aligns future billing cycle dates. It sets the day of week for week intervals, the day of month for month and year intervals, and the month of year for year intervals. The default value is either the subscription creation date or the trial end date (if you’re using a trial period). You can also explicitly set this value at the time you create the subscription.

The following are examples of monthly subscriptions with different billing cycles:

• A monthly subscription with a billing cycle anchor date of September 2 always bills on the second day of the month.
• A monthly subscription with a billing cycle anchor date of 31 January bills the last day of the month closest to the anchor date, so 28 February (or 29 February in a leap year), then 31 March, 30 April, and so on.
• A weekly subscription with a billing cycle anchor date of Friday, 3 June bills every Friday thereafter.

Full billing periods start on the first full invoice date, which is often the same as the billing cycle anchor and is always interval-aligned with it.

Specify the billing cycle anchor for new subscriptions

There are two ways to set the billing cycle anchor on new subscriptions:

• Use billing_cycle_anchor_config to calculate the timestamp for you (monthly or yearly subscriptions only).
• Use billing_cycle_anchor to accept the timestamp directly.

If you’re creating a monthly or yearly subscription, we recommend using the billing_cycle_anchor_config parameter because it automatically factors in short months and leap years for you. If you’re creating a daily or weekly subscription, or if you prefer to set the cycle date of your subscription using a timestamp, use the billing_cycle_anchor parameter directly.

Use billing_cycle_anchor_config

To create an integration with monthly and yearly subscriptions, use billing_cycle_anchor_config on create subscription to specify the day of the month on which to anchor.

Set day_of_month to 31 to create a monthly subscription that cycles at the end of the month, even in months with less than 31 days. If a month has less than 31 days, the subscription cycles on the last day of that month.

curl https://api.stripe.com/v1/subscriptions \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d customer=
{{CUSTOMER_ID}} \
  -d "items[0][price]"=
{{PRICE_ID}} \
  -d "billing_cycle_anchor_config[day_of_month]"=31

You can also specify month to control the month of year for the anchor on multi-month and yearly subscriptions.

To cycle your yearly subscriptions on the first of July, create a yearly subscription with a month of 7 and day_of_month of 1.

curl https://api.stripe.com/v1/subscriptions \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d customer=
{{CUSTOMER_ID}} \
  -d "items[0][price]"=
{{PRICE_ID}} \
  -d "billing_cycle_anchor_config[month]"=7 \
  -d "billing_cycle_anchor_config[day_of_month]"=1

To precisely align billing periods with another subscription, provide the same day_of_month as the original as well as the same hour, minute, and second. If you omit the hour, minute, and second parameters, the values derive from the time of subscription creation.

For example, if you have an existing monthly subscription with a billing_cycle_anchor timestamp that contains the day of the month, hour, minute, and second of 15, 12, 30, and 0, you can align a new monthly subscription with it. To do this, set day_of_month, hour, minute, and second to match those same values, respectively.

curl https://api.stripe.com/v1/subscriptions \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d customer=
{{CUSTOMER_ID}} \
  -d "items[0][price]"=
{{PRICE_ID}} \
  -d "billing_cycle_anchor_config[day_of_month]"=15 \
  -d "billing_cycle_anchor_config[hour]"=12 \
  -d "billing_cycle_anchor_config[minute]"=30 \
  -d "billing_cycle_anchor_config[second]"=0

If you use billing_cycle_anchor_config, it might result in a billing_cycle_anchor that’s more than one billing period in the future. However, the date for the first full invoice always falls within one billing period from the creation of the subscription or the ending of a free trial.

For example, assume that you create a two-month interval subscription in February and you cycle it at the end of every month by setting day_of_month to 31. The next month that has 31 days on two-month intervals from February is August, which results in a billing cycle anchor on 31 August. However, the first full invoice date for this subscription still occurs in February. There’s an initial, prorated period from subscription creation until 28 February (or 29 during a leap year), followed by a full two-month billing period.

Use billing_cycle_anchor

You can create a subscription with an explicit billing cycle anchor using the Subscriptions API or Checkout.

curl https://api.stripe.com/v1/subscriptions \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d customer=
{{CUSTOMER_ID}} \
  -d "items[0][price]"=
{{PRICE_ID}} \
  -d billing_cycle_anchor=1611008505

Change the billing cycle on pre-existing subscriptions

Use the Subscriptions API or Dashboard to change the billing date of an existing subscription through one of the following options:

• Reset the billing cycle anchor to the current time.
• Add a free trial to automatically set the anchor date to the end of the trial. Trials typically start when you create a subscription, but you can also apply them to existing subscriptions, allowing you to credit the customer for the days left in the previous cycle that they already paid.
• If all the prices are zero-amount, adding one or more paid prices immediately resets the billing period. See the upgrade and downgrade guide for more details on this scenario.

Reset the billing cycle to the current time

When you reset the billing cycle, Stripe immediately sends an invoice. Enable proration to credit the customer for any days already paid in the previous period. Disabling proration might result in overcharging your customer.

curl https://api.stripe.com/v1/subscriptions/sub_49ty4767H20z6a \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d billing_cycle_anchor=now \
  -d proration_behavior=create_prorations

Add a trial to change the billing cycle

Adding a non-prorated trial period to an existing subscription allows you to configure the billing cycle to be any date.

Typically, if you’re using the trial period to change the billing cycle without issuing a prorated invoice, you disable proration because the length of the trial period accounts for the portion already paid from the previous billing cycle.

For example, if a customer has an active subscription set to bill next on 23 July, and you introduce a trial period until 1 August:

• The customer receives a 0 USD invoice on 15 July.
• The customer isn’t billed on 23 July.
• The customer is billed next on 1 August, then on 1 September, and so on.
• The customer already paid until 23 July in the previous cycle, so that “free” period isn’t actually free.
• The period between 23 July and 31 July isn’t charged.
• The new cycle billed on 1 August is a full cycle at the normal rate.

curl https://api.stripe.com/v1/subscriptions/sub_49ty4767H20z6a \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d trial_end=1611008505 \
  -d proration_behavior=none

Metered billing

With metered billing, the price paid by the customer varies based on consumption during the billing cycle. When changing the billing cycle results in ending a subscription interval early, you charge the customer for the usage accrued during the shortened billing cycle.

Thresholds

In addition to the regular cycle, you can configure subscriptions to bill whenever the amount due reaches a threshold.

If you have a subscription configured to invoice this way, you can set it up to reset the subscription cycle when it hits the threshold.

See billing thresholds for more details.