#fumi-subscription-events

1 messages · Page 1 of 1 (latest)

bold stirrup
#

Hi 👋 customer.subscription.deleted is the correct event to listen to if you want to be notified of a subscription ending.

golden hazel
#

Hi thanks. But I want to divide users into two groups which want to and don't want to end the subscription.
If users want to end the subscription, customer.subscription.deleted will occur.but
Although users don't want to end the subscription , I want to change the kind of their subscription which will downgrade , changing the price of the plan.
So users won't end subscription , I think customer.subscription.deleted may not occur.

bold stirrup
#

It sounds like you want to trigger an update to a subscription based on your customers telling you want they want to continue the subscription, does that sound right?

golden hazel
#

yes

#

Should I use Subscription Schedules API ?

bold stirrup
#

If you want to schedule the changes to occur later, then yes subscription schedules would be a good fit

golden hazel
#

thanks! ok.
The plan all users subscribe will end in one month.
But only users who don't want to continue tell us they want to end the plan .
and we want to change the type( price and contents) of plan users who want to continue the plan automatically.

#

Is there the way other than subscription schedules?

bold stirrup
#

Oh, so you want everyone's subscription to change to this new price unless they explicitly opt-out?

golden hazel
#

Thanks yes!

bold stirrup
#

Gotcha, subscription schedules are still the right way to do this, but if you are building an opt-out flow instead of the opt-in approach you mentioned earlier then you can just create every subscription on a schedule and only cancel if the customer opts out.

golden hazel
#

thanks , but I create the plan , not using schedule api. So Should I create the plan again , using schedule ?

deep pollen