#Ajay479

1 messages · Page 1 of 1 (latest)

sturdy tangleBOT
boreal marsh
#

Trying to create a subscription that starts in the future

cold talon
#

Hi, going through your old thread.

#

Unless, you'd like to add more details here

boreal marsh
#

Thank you, no rush

#

Using .net if that helps

#

I could go the trial route from previous thread but that seems hacky to me

How hard is it to upgrade our stripe version?

cold talon
#

When you try creating the Subscription Schedule, what error are you seeing?

#

I realize you're not talking about the Stripe API version here. You're referring to the .Net Client library, is that correct?

boreal marsh
#

Yes that is correct, sorry I should have specified

#

I am trying to create a new SubscriptionScheduleCreateOptions object but not able to do so, I am assuming this is because we are using a really old stripe library

gilded leaf
#

Hello! I'm taking over and catching up...

#

You are indeed on a really old version. 😅

boreal marsh
#

Do you know of anyway to schedule subscriptions with the version that we are on or should I just go the trial route?

gilded leaf
#

I guess you could make the raw API calls yourself, but that would probably be a lot of work. I recommend upgrading to a newer version of the library if at all possible.

boreal marsh
#

Is the link above relevant to upgrading our library?

#

I am fairly new developer so not exactly sure how to upgrade a library 😅

gilded leaf
#

Ah, upgrading from such an old version is not trivial, unfortunately. Step one would be to read through the changelog from your current version up to the version you want to upgrade to, and audit your code to see what changes need to be made: https://github.com/stripe/stripe-dotnet/blob/master/CHANGELOG.md

You should also have a look at the migration guides in the right sidebar here: https://github.com/stripe/stripe-dotnet/wiki

Then you would upgrade in your test environment, make the required changes, confirm everything works, then deploy to production.

boreal marsh
#

Oh yikes... well that helps for sure! Guess I better start reading

gilded leaf
#

Before you dive into all of that, can you tell me what your goal is at a high level?

#

I want to make sure I'm sending you down the right path. 🙂

boreal marsh
#

Of course I will try and keep it simple

We are trying to make a way to "add" stuff to a subscription

So user has a subscription to a,b for $10 a month

They want to add c,d for another $10 a month

I want to charge the user $10 for adding those items c,d immediately then once their original subscription is over, charge them $20 a month

#

The issue is I think we did a weird implementation, at the time of checkout we

Check if they have an existing plan (if so delete it)

Check if they have any subscriptions to that plan (if so cancel them)

Then we create a new plan and new subscription

#

That might not be very high level...

gilded leaf
#

Hm. You can modify an existing Subscription and add one-time line items to the next Invoice.

#

Would that work? You could add the new recurring items c,d, and then add a one-time payment on top of those.

boreal marsh
#

Well as far as I can tell the only thing determining how much we charge the user is the plan that we are subscribing them to...

Let me get an example pulled up in my debugger

gilded leaf
#

Right, but you can have more than a single Plan/Price per Subscription.

boreal marsh
#

Ah, so you are saying create a new plan for c,d subscribe them to that then charge one time?

gilded leaf
#

So, honestly, there's going to be a lot lost in translation between the way things were done back on the version you're using now vs. today. Your integration is many years old, and back then there were likely a lot of limitations that do not exist today.

#

For example, today Subscriptions use Products and Prices, but Products and Prices did not exist at the time 10.0.0 was released.