#afhaque
1 messages ยท Page 1 of 1 (latest)
(Snufkin. You are insanely helpful. I don't know how you do this)
(You helped me with a few other issues in the past)
Hi ๐
This one sounds pretty tricky. Since there are only a couple ways I could see this working.
Yuckk. If I have to I can just change the name of the product each time to reflect the length of the subscription. But then I'd need a way on the back-end to set the date when the subscription would end.
(Suggestions on where to start with the latter would be appreciated if that's my best bet)
My first thought would be to create a Subscription Schedule from the Subscription created by the Checkout Session and have the phase run for a specific set of iterations.
https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases#installment-plans
(Okay. One more wrinkle. We're a platform that uses stripe connect through which all our non-profits connect. So would this still be possible for us to do centrally?)
That depends on how the Platform and Connected accounts are set up and how the checkout session is configured.
I need to step away but my colleague @bold sun will be able to help.
Thank you!
๐
Thanks karbi!! One more possible avenue I'm trying to explore is whether it's possible for me to use cancel_at on the checkout session creation... I'm not seeing it as a parameter available for subscription_data on the checkout object though...
(Will let you catch-up)
Right now there's no way to set cancel_at up-front during Checkout Session creation
Okay good to know. ChatGPT clearly got this wrong ๐
So I can look into the suggestion snufkin offered and perhaps as an alternative set up some kind of webhook that modifies subscriptions we create and adds a cancel date after the fact?
Any other recommendations on directions I should explore?
(It's good to know that I wasn't missing something super obvious)
Snufkin's suggestion of using the SubscriptionSchedule to configure cancellation after the subscription has been created is likely the best option