#kratos6753-subscription schedule
1 messages ยท Page 1 of 1 (latest)
๐ happy to help
you can always start by creating a subscription and then create a subscription schedule from that https://stripe.com/docs/api/subscription_schedules/create#create_subscription_schedule-from_subscription
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
or you could simply use the default_settings https://stripe.com/docs/api/subscription_schedules/create#create_subscription_schedule-default_settings
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
it's really up to you
ok, what is the benefit of creating a schedule then? Can I create future dated subscription using create subscription api?
subscription schedules is meant to be used to describe a more complicated with subscriptions that uses different plans/prices inn each phase
Can I create future dated subscription using create subscription api?
yes you can
but it would be another subscription
for each phase
which is sometimes not the desired result
Ok. What I'm thinking for my use case is. Create a schedule with creates subscription on future date, whenever subscription is created, I would listen for that event and then update subscription to have payment behavior to default_incomplete. So, it will be incomplete until my first invoice payment happens. How does it sound? Basically, I want to associate active status with current billing paid.
Also, please let me know the difference between default_incomplete vs allow_incomplete ---> these are payment_behavior options. When to use what?
This is highlighted in the API reference: https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_behavior
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I would listen for that event and then update subscription to have payment behavior to default_incomplete. So, it will be incomplete until my first invoice payment happens
Not sure if that would work as the initial invoice will already have been generated. You should try testing it!
Ok, will test it.