#dominikalexander - Subscriptions

1 messages · Page 1 of 1 (latest)

last hill
#

Hi, what's up?

#

Is it possible to have an 9.99 Package they can subscribe to but there is an minimum "contract" for 3month before they can cancel the package

#

Quoting here to keep everything together

green oasis
#

great thank you

#

i updated my message

last hill
#

dominikalexander - Subscriptions

#

So in this case we are talking about a Subscription you want to set up, correct?

#

Where you bill 9.99/month with a minimum of 3 months?

green oasis
#

I only have a subscription model like 9.99/month but i want the customer to have the option to cancel only every 3 month

#

He subscribes and then he pays 9.99 each month an when he cancels it will still run 3 month before it stops

last hill
#

Okay, perfect.

#

So actually that is totally within your control. Your integration can control when you allow a user to cancel their subscription.

#

It would just mean you would need to build that part of your integration to schedule subscription cancellations on a 3 month period.

green oasis
#

Is there a cronjob like check or how will that work ? Some self hosted solution checking all subscription and updating them every day ?

#

Or is it possible to use webhooks ?

last hill
#

We don't have any hosted solution that offers that level of granularity. It would. be up to you to build the interface and business logic.

#

So you could build an interface to allow the user to manage their subscriptions and then it would be up to your server logic to determine when to trigger the cancelation of the subscription.

#

Could you give me a more clear example of the workflow you are thinking of?

#

Does a user only have the option to cancel every 3 months? Can they cancel any time but it only takes effect 3 months after they cancel?

green oasis
#

No package is monthly bookable (Its always a 3 Month period).
But payment will be monthly.
When a user cancels 30 days before one 3 Month period is ending the subscription will end otherwise it will add another 3 Month period and will end after that.
I hope its understandable 😄

last hill
#

Your server would still need to use the 3 month period and 30 day logic you described above on your server to determine the appropriate behavior.

#

In fact it would make sense to just have a monthly subscription that bills 9.99 each month

#

But when your user hits the "cancel" button your server would check where they are in their cycle (you would keep track of this on your server) and, based on your logic, you could create a subscription schedule to modify the existing subscription with a set number of iterations.

#

You can configure the end behavior of your schedule to make sure the subscription cancels.

green oasis
#

Great THANK YOU for your effort! I got the idea now and how we can solve it.
I think to start right away the best solution is probably to deactivate the cancel button completly and let them cancel via mail and we track it manually for now until the solution is developed