#koden-elements-subscriptions
1 messages · Page 1 of 1 (latest)
koden-elements-subscriptions
@analog torrent usually what you do is your start by accepting a payment for the first subscription, save payment method details as part of this. And then you can start other subscriptions with that saved payment method if needed.
There isn't a "start 3 subscriptions at once" kind of flow. If you want 3 separate Subscription objects then you have to start each one separately
Ahh that makes sense. Thanks @tidal siren !
Let's say as a customer, I want to purchase a one-time product, but I also have 3 other products that I'd like to subscribe to in addition to that, would I be able to use Stripe Checkout for this scenario?
It depends. Are all the "recurring products" on the same billing cycle? Like all monthly Prices that the customer will pay all at once? Or do you want 3 completely separate Subscriptions?
some may be the same billing cycle, but there could also be another product with a different billing cycle
it's important to know really
There could be different billing cycles yes
If they are on different billing cycles then you need to start separate subscriptions
So you can't do what you're after with one payment in Checkout in that case
Hmm I see; what if we use the Save and Reuse API, and subsequently create individual subscriptions
That will work, the thing to consider is that creating new subscriptions means each will charge separately. That will slightly increase the Stripe fees you get and can mean three opportunities for the user's banks to ask them to do some separate authorization
So that will work, but if you can group things on the same cycle to the same subscription, that might be easier.
That is very valuable info @sonic breach . Thank you to both of you. I'm mainly looking from a high level how I'm going to do this and this help provide that roadmap. Thanks so much you guys
Of course! Glad we could help. Let us know if you come across anything else