#mr_pablo
woven drift
pastel condor
I think that may depend on how the subscription is cancelled. How are you/the customer cancelling it here?
acoustic pawn
what ways are there?
shy hamlet
👋 stepping in as Pompey needs to step away
They webhook fires when the Sub cancels. So if cancel_at_period_end is set, then it won't fire until the sub actually cancels at the end of the cylce.
If you are calling the Sub Cancel endpoint then it fires immediately
shy hamlet
acoustic pawn
So when you say "If you are calling the Sub Cancel endpoint then it fires immediately" this is only true if you do not set "cancel_at_period_end" ?
where would a customer be able to call the endpoint immediately, without "cancel_at_period_end" being set?
shy hamlet
Are you using Customer Portal?
Or are you managing these Subscription updates via your own integration?
acoustic pawn
Possibly both, I'm not sure yet, hence gatehring info
If the Portal does not allow the setting of "cancel_at_period_end" then we would likely not use the Portal
shy hamlet
It does allow for that. See: https://stripe.com/docs/api/customer_portal/configurations/create#create_portal_configuration-features-subscription_cancel-mode where you can indicate what the cancel mode should be
acoustic pawn
OK. So in what scenario would this happen? "If you are calling the Sub Cancel endpoint then it fires immediately"
shy hamlet
If your integration uses: https://stripe.com/docs/api/subscriptions/cancel. Or you set the Customer Portal configuration to cancel immediately.
acoustic pawn
Ah, so via the API, cancel sub and update sub are different, and to cancel at the end of the period, you actually use "update" ?
shy hamlet
Correct.
acoustic pawn
👍
if i set "cancel_at_period_end" via update, can it be set back, if the customer changes their mind?
acoustic pawn
Cheers, thanks