#akzentmayer_unexpected
karmic rapidsBOT
đź‘‹ 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/1324471435179065344
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
fierce latch
Hello, we reset the billing cycle anchor to the current time if you switch between cycle lengths. If you have prorations turned on for the update, that will immediately create an invoice
If you want to avoid creating the invoice, you can specify proration_behavior='none' when making the update call
wispy scarab
We did set that on the subscription update call!
the resulting payment intent says it was created from that specific update call
pi_3Qcu0qGcOvBbq6Ss1QJ6khTC
fierce latch
Gotcha. Looking in to that ID and will let you know what I can find.
wispy scarab
thank you!
fierce latch
Oh right, this isn't considered a proration. That is the full price for the new cycle
wispy scarab
From the update subscription docs:
If you don’t want to prorate, set the proration_behavior option to none. With this option, the customer is billed 100 USD on May 1 and 200 USD on June 1. Similarly, if you set proration_behavior to none when switching between different billing intervals (for example, from monthly to yearly), we don’t generate any credits for the old subscription’s unused time. We still reset the billing date and bill immediately for the new subscription.
fierce latch
A proration would credit the leftover time on the cucle that got interrupted.
Yep there we go, that is what the doc said.
Trying to think of what you can do here.
wispy scarab
Ok so because it's a cycle change Stripe automatically charges
In our code we can avoid sending a one time invoice for cycle changes and let Stripe handle charging
fierce latch
Oh nice, yeah if it works for you to let us handle sending out the invoice then it sounds like no change needed then.
wispy scarab
i need to look into this code a bit longer.. it's possible we're doing something specific with the one-time invoice though where we need to do it instead of stripe. if this is the case, is there any way to mitigate that auto invoice generation and charging?
fierce latch
I don't think you can prevent the invoice from being generated so I think you would need to cover the payment in some way. I think the two most common ways to do that would be with a coupon or with a credit note.
Or you could temporarily switch to a $0/yr price and then your normal yearly price after.
wispy scarab
ok! hopefully we can just let stripe do it's thing and avoid that workaround