mckeemi_unexpected

[wispy notch]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1412383161870192811

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[lean dune]

Can you share some object IDs and/or request IDs please? sub_sched_xxx etc

[primal rapids]

Yes no problem 2 mins and I'll get some, I've been trying different variations

It's using Connected accounts the subscription Id is sub_1S0fDyGzqfG4XYbWVxwJduhv and the connected account Id is acct_1Rxmw5GzqfG4XYbW

[lean dune]

This request, right? https://dashboard.stripe.com/test/logs/req_GgvyA16ZS4fNQr

[primal rapids]

Yes that's the one, I updated the schedule on 27th August, an invoice was paid that morning at the wrong price, so updated the schedule and an invoice came out the same day when I updated

I have tried various approached, i.e. putting a start date in etc but have got a different Stripe exception thrown with the alternatives.

I need to keep the existing subscription

[lean dune]

This is mostly due to the nature of the upgrade – you're transitioning from a monthly price (price_1S0fDyGzqfG4XYbWWs0Ex83c) to a weekly price (price_1S0kkMGzqfG4XYbWWagrNGBu)

In that situation we will always reset the billing anchor. This, paired with the fact your passed proration_behavior: 'none', means we will immediately bill them for the new price upfront:

When prorations are disabled, customers are billed the full amount at the new price when the next invoice is generated.
https://docs.stripe.com/billing/subscriptions/prorations#disable-prorations

What exactly are you trying to do in the update?

[primal rapids]

update the price and interval of the current subscription, so e.g. if it was original £50 monthly and we wanted to change it to £10 weekly we would thenext invoice to be from the next week or ideally from a date we pass in.

sorry just read that back!

just want to have the flexibility to switch someone to a different payment plan

[lean dune]

But you want to persist the existing billing date?

You're going to need to add a new phase that starts at the desired upgrade timestamp, rather than updating the existing phase

[primal rapids]

Ifwe could even specify the next payment date and kick off the updates from there as it depends on whether they have paid this month or not if you know what I mean

[lean dune]

So phases[0], monthly, ends on X, and phases[1], weekly, starts on X

[primal rapids]

So if I end the current phase at a timestamp and start the new phase at the same timestamp+1 day?

or do they be set to the same timestamp?

[lean dune]

It'd need to be ~immediately after (same timestamp AFAIK)

[primal rapids]

That's great, I understand it's continuous. One last thing, I don't need to use FromSubscription or anything like that in the update? The associated subscription picks up the schedule changes I assume?

[delicate wren]

hi! I'm taking over this thread.

[primal rapids]

Hi

[delicate wren]

if you update an existing schedule, then no need to use from_subscription.

[primal rapids]

Brilliant, I think when I tried different things the fromSubscription I had added in caused some issues with what I set. I will try to resolve by updating the currentPhase to end at timestamp and add a new phase with the new price and same start at timestamp