#jaketoolson
1 messages · Page 1 of 1 (latest)
Hi there. Why do you think you might need subscription schedules?
I feel like an idiot but I can't tell much of the difference but what I do see in a schedule, is the ability to set a start date. I do recognize the additional complexity of phases but I don't think that is something I need either. BUT maybe I do because if I have an existing "monthly" interval subscription, and I need to add another line item to this specific item at a pro-rated rate for the duration, maybe I can use phases?
I've made some basic API integrations this week but have hit a wall not knowing if I'm utilizing stripe for my needs effectively.
Hi, stepping in here as codename_duchess is away.
ultimately I need the ability to set a start date, interval, and add/update line items haha. I want my cake and to eat it too but my experience with fintech has been basic e-commerce style. This is a whole new beast.
What we do right now is manually create subscriptions (not schedules) in the gui, and a new product/price is the "hire".
so exploring how I can automate this and my brain is exploding (hit a wall after a week of coding/tests) so I'm seeing if others might be able to offer some input
No worries, I'm happy to provide as much information as needed to get this clarified. You can learn more about Subscription Schedules use cases here, https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases
It typically is used when you need a more complex subscription logic with added layers of discounts etc.. I think the document will provide a bit more clarity.
The use cases you provided above would work with Subscription Schedules. You can use both Subscription and Subscription Schedules depending on the specific scenario.
🤯 haha.
the biggest complexity I can think of is, having an existing subscription, and I need to add a line item to it and pro-rate that line item for the current billing cycle, but after that no proration.
and thats why I have hit my wall - as I'm down the rabbit hole and am just uncertain.
so I'm wondering if I start off using a normal subscription that re-occurs monthly... and when I need to add to it by adding a line item that pro-rates, I associate it to a subscription schedule and 1 phase and after phase end, the pro ration is gone and it returns to normal monthly billing
and is there a way for me to test my theory using iterations and phases ? Seems like I should set the interval to day and check after a day to see if the transition (proration) etc work
I see, thank you for providing the added context. Just to confirm, you'd have a monthly subscription, then on month three as an example, you'd add an invoice line item. Then on month 4, it would go back to it's normal monthly pattern, is that correct?
We have built Test Clocks to exactly test your subscription integrations, https://stripe.com/docs/billing/testing/test-clocks so you might want to play with this. This way, you would not have to wait around to run through scenarios. Here are the steps to getting started: https://stripe.com/docs/billing/testing/test-clocks#create-clock
OOOoOOOoOo ^ Test clocks are perfect!! Thank you.
Yes, a subscription may start with 3 line items, and on 1/2 way into the second billing cycle (as an example), we need to add a 4th line item and pro-rate that line item for the duration of the billing cycle (lets say 15 days) after which the pro-ration will end, and all 4 line items will continue to be billed in full
using this use case, is this something I should continnue to explore using subscription + sub schedule and phase?
I honestly think that you could just use Subscription, and when you need to add an invoice item, you can make the Update Subscription call, https://stripe.com/docs/api/subscriptions/update. So I'd recommend that you start testing with just Subscription and see if that solves your use case which I highly think it will.