#jonah-subscription-cancel
1 messages ยท Page 1 of 1 (latest)
jonah-subscription-cancel
For #1, if you cancel, the Subscription is done/canceled and it's a terminal state. If they want to resume their Subscription in a few months you would create a brand new Subscription
for #2 you would use the Update Subscription API, see https://stripe.com/docs/billing/subscriptions/upgrade-downgrade
For number 1, would it then be recommended to pause forever until they resume again?
that's really up to you really, depends what you want out of this
Users have a 30-day cycle. They can choose to "pause/cancel" and then just "resume" it again at a later date.
Most convenient for them would likely be to just pause. I'm missing the upside to cancelling beyond docs jargon.
We don't really have a "pause" logic in our API. So you either cancel, or switch them to a free Price maybe in the meantime. It's really up to you as a business to decide what fits best for you
Ah
So "pause payment collection" could effectively be the pause
And it's my choice what to do on the front-end when the "payment collection" is paused.
no I would recommend never use "pause payment collection" at all for your use-case.
It was built for something drastically different like during COVID when most businesses wanted to stop charging their customers entirely while they figured things out
Gotcha.
So cancel, but just keep then keep payment info so we can just create a new subscription whenever the user wants to resume
yeah that's what I'd do
Okay, only caveat here:
if they cancel before the end of their cycle, then create a new one.... is there a simple way to not charge them for the new one until the end of the current cycle?
https://stripe.com/docs/api/subscriptions/create#create_subscription-cancel_at_period_end use this instead in that case
that marks the Subscription to cancel at the end of the current period. And you can undo it (set it to false) if they change their mind
Would the cancel_at_period_end be called in subscription.update?
You sent the create_subscription url
And I see there's params for that at both.
So if cancel_at_period_end is passed in on creation, I'd assume this would only matter if I then call subscription.cancel.
And then would have to subscription.update if I want to cancel.
Or maybe I can do it both ways?
yeah both ways work, it exists on create and update
Do you recommend having it just use the previous payment information in the new checkout links?
I don't really understand what that could mean
what's a "new checkout link" exactly?
e.g, if they renew a cancelled subscription
Are you talking about Checkout, our product? Or something unrelated?
checkout ya
Checkout?
Yea
sorry, I'm nitpicky, but every developer says "checkout" for their own payment form ๐
lol you say Checkout again with no capital C :p
Then you don't really control any of this yourself really. But yes, you send them to a new Checkout Session's URL and it would have the existing Customer id cus_123 associated with that Session. In that case we (Stripe) will show their previously saved card if any yes
A Checkout Session expires after 24 hours though so that won't really work
will that subscription wait to set a new expiry date until the payment is filled?
No I mean for automatic renewal. Sorry
I'm so sorry, I have no idea what any of this could mean. You seem to be using the Stripe vocabulary a bit differently so I'm totally lost ๐
Can you maybe give concrete examples with example dates of what you mean?
Okay, so my subscription has 30-day renewal cycles.
After 30-days, it will bill again. But on the second time, the payment fails.
I want the 30-days to start from when the payment succeeds again, i.e, the user changes their payment info.
What's the best way to call the APIs so that works out?