#tas0458

1 messages · Page 1 of 1 (latest)

terse mortarBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

modern sun
#

Hi, let me help you with this.

#

I am not sure I understand. Could you please describe an example use case? What and when do you expect to happen?

tired valve
#

so, this is to implement a early renew / pre-paid capabilites.

For instance, there is a user with a current active subscription. If he wants to extend its cuurent subscription and append 1 more year to it, he could pay in advance and upfront for this extra year. This way, he does not need to wait for the renew period

#

so

#

I have already set a webhook

#

that listens for checkout.session.completed event

#

and whenever a customer purchases the 200$ one off product, I should grant an additional year to the user's current subscription

#

and when I get the webhook event, I should create a schedule on the user current subscription

#

and using subscription schedules for a user with an existing subscription, and appending one year of the $0 price/product to that schedule,

#

does it make sense?

modern sun
tired valve
#

not sure If a get this.
do you think the approach I described would not work?

modern sun
#

I tried to describe the approach you are looking for with Stripe terms.

#

You don't need Subscription Schedules for that.

#

For most cases Subscription Schedules is an overkill.

tired valve
#

let me break down your response to make sure I understand

You can have a $200 Subscription with 100% discount (this is for the new product, right?)

And then set cancel_at to the end of the cycle (this is for the new product or the current subcription?)

and then you update it to the end of next cycle (which subscription are you referring to?)

modern sun
#

You will only have one Subscription object for $0. It will be used to check if it's active for a given customer to see if you should provide your services to them.
After they paid for the first time, you will set the cancel_at to the end of the 1st billing period, e.g. they started on 15th of Feb 2024, then cancel_at will be set to 15th of Feb 2025 (as Unix timestamp).
Then you can give them the ability to create and pay a one-time $200 Invoice. When this happens, you will reset cancel_at to 15th of Feb 2026.
If they don't, the Subscription is cancelled at the end of the period.

#

This basically detatches the payments from the Subscription objects, and uses it merely for tracking the Subscription status.

tired valve
#

TY for your response.. just need some time to diggest all this info lol

#

and for comparison purposes, how could I achieve the same with subscriptions schedules?

modern sun
#

I don't think I see a straightforward way to do this with SSes

terse mortarBOT