#zaddler_code

1 messages ¡ Page 1 of 1 (latest)

tulip shardBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1217569894166696008

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

desert shaleBOT
#

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.

spare shuttle
#

In your scenario, are you doing prorations at any point?

spare shuttle
#

Stripe subscription's don't really track this situation, so they don't remember what plan they had two updates ago. I think you will need to record on your side what the highest tier this subscription has been on this month and then charge or not charge based on that when updating your subscription

urban gust
#

What I want is like... downgrade it from the plan, but if it goes up again without the billing cycle happening first, something like renewing that plan

spare shuttle
#

From what you have described so far I think that would be necessary. Can you give me an example of what the renewing thing would look like with your three example prices? Not quite getting that scenario but I am happy to consult

urban gust
# spare shuttle From what you have described so far I think that would be necessary. Can you giv...
  1. User purchases a subscription of 3.99 (Billing would be May 1 to June 1.

  2. Then at that same moment you want to downgrade to a 2.99 plan (I would charge you on June 1, when the May-June cycle ends. For Stripe it is on the 2.99 plan but for my system it is on the 3.99 plan) .

  3. If at that same moment the user changes from 2.99 to 3.99 (which was billed from May 1 to June 1), Stripe will charge them for the plan change while in the billing cycle, when what they should do is , renew it, that is, return to step number 1, which is to return to the cycle from May 1 to June 1.

desert shaleBOT
spare shuttle
#

Oh, so you want to charge the full 3.99 again even if you are not all the way through the cycle? You can do that by resetting the billing cycle anchor while updating your subscription

urban gust
#

I understand, but how can I know if the user has already paid for an expensive plan while in the billing cycle? Because the problem is that, I have a logic that when it changes from cheap to expensive, it always invoices at the moment, and collects, but if it pays in the same cycle, it goes down and goes up again, how could it know that I already paid in the cycle of billing?

wintry finch
#

Hi, taking over as Pompey needs to step away. Let me catch up here

urban gust
#

Alright

#

Is there a way to know which is the most expensive plan that a customer purchased within the current billing cycle on the current date?

wintry finch
urban gust
#

It could be but it is not very practical, I would like to know if there is a way to obtain the current invoice for the current cycle

#

Because that way I can charge or not being in the current cycle

#

If it came from an expensive plan already paid for, it goes down and goes up again, what I want is how to renew it, not charge you again

wintry finch
urban gust
#

I think so, the subscription returns latest_invoice, in latest_invoice I can verify which was the most expensive plan I paid for

#

I'll try to find a solution to that, thank you very much!