Thunderducky

[timber fossil]

It could potentially need the subscribing party to come back on-session if payment needs 3DS or additional action to complete

actually maybe not - let me think for a minute

I think this would work:

• You have the existing subscription and set it to cancel at period end
• You create multiple new subscriptions with billing_cycle_anchor set to the end date of the existing subscription and you set backdate_start_date to the start of the current cycle of the existing subscription and you set proration_behavior: none (https://stripe.com/docs/billing/subscriptions/backdating?dashboard-or-api=api#backdating-no-charge)

This should create those new subscriptions without needing a charge up front - the first charge will be due on the billing cycle anchor date, when the original subscription cancels