#bhanu365 - subscription schedules
1 messages · Page 1 of 1 (latest)
Hello, I am not sure I understand your use case here. Can you tell me more about what you are trying to do here?
Like is there a reason that creating a normal subscription schedule would not be sufficient?
Let me explain you briefly
First the user can buy the normal subscription using Subscription::create method
After that If a user cancel their subscription
They can buy another subscription but that subscription will be start after previously subscription end
So in that case I need to schedule my subscription on the behalf of preciously subscription cancel date
In that case you should be able to create a schedule that starts a new subscription in the future https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases#start-subscription-future
Or is that not quite what you are talking about?
Please check first message that I want
Is there any parameter that I can set before the confirmation and then I can set after the confirmation. If don't set the confirm then the subscription schedule will not be start.
Unfortunately schedules don't work like that as they won't take payment up front if they start in future. You may want to do something like create a separate PaymentIntent and then create or not create this schedule based on whether that payment intent succeeds or not
Depending on what you are doing, you can have the schedule use a $0 price for the first cycle as that has already been paid
Is there is any link where I can see the preview of subscription schedule and can see how it's working?
Do you mean in the dashboard in general or are you asking about a something on how schedules generally work?
No i'm asking about the demo if you have any demo
Hi 👋 I'm stepping in for @whole thorn
The easiest way to see how subscriptions work (currently) is to use the code in our quickstart test out building simple subscriptions:
https://stripe.com/docs/billing/quickstart
I am asking about only scheduling subscription
Okay, the simplest approach is to build out a basic scripted integration and play around with them: https://stripe.com/docs/billing/subscriptions/subscription-schedules
We also provide a useful testing feature called Test Clocks that allow you to simulate time advancing. This lets you test out subscription features without having to wait 30 days to a year to see what happens.