#eloquence2484_api
fringe ravenBOT
👋 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/1278792088712122508
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
robust meteor
Right now we're considering creating 2 immediate phases to get the behavior we want, where the second one has billing_cycle_anchor=start_phase. But this feels a bit hacky...
languid sapphire
Hi, we document how proration works with backdated subscriptions here: https://docs.stripe.com/billing/subscriptions/backdating?dashboard-or-api=api#backdating-no-charge. If you specify prorations to none, you are telling Stripe not to charge the customer. However, if you rather charge the customer, you would want to look here: https://docs.stripe.com/billing/subscriptions/backdating?dashboard-or-api=api#backdating-charging.
After reviewing the above documents, let me know if you have any follow up questions.
robust meteor
Thanks! Yes, we'd like to create an invoice immediately, but we do not want it to prorate. The case is this:
Subscription migrated (with no payment/charge) on May 1st
Subscription should renew on May 15th (this is the billing cycle from the old system)
On May 15th we'd like to generate an invoice for the full monthly amount and reset the billing_cycle_anchor as well, so the next renewal will happen on Jun 15th (for monthly subs). But we would not like to do that with a long phase from May 1st to May 15th, as that breaks some flows/use cases where customers can change things in the meantime.
languid sapphire
When you create the subscription, you can pass the new billing cycle anchor along with the backdate: https://docs.stripe.com/billing/subscriptions/backdating?dashboard-or-api=api#backdating-billing-cycle. I highly recommend testing this using your Test API key and our Test Clocks: https://docs.stripe.com/billing/testing/test-clocks. This tool allows you to change time as you test your subscription integrations.
robust meteor
Thanks, we've been using test clocks a lot 🙂 Can I backdate the subscription start, set the billing anchor, and ALSO not prorate when creating the (migrated) subscription then?
languid sapphire
Yes, from what you're saying. However, I recommend going through the above documents and try passing these three parameters when creating the test subscription.