kamal-singh_api

[little tree]

👋 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/1334832731971911781

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

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.

• kamal-singh_api, 1 hour ago, 11 messages

[unreal bolt]

👋 happy to help

would you mind sharing the request ID for the subscription upgrade?

[wraith vault]

where can i find reqid

here it is req_q3WZHkngLawvSv

[vernal heath]

Taking a look

It's because you're applying a coupon, I think

[wraith vault]

without the coupon its doing the same thing

see this event evt_3QnHLHJrW4qoE0zy0AYjsb3Q here i tried to upgrade from 6 to 8 which is from $54 to $72

[vernal heath]

Please share request IDs, not events

[wraith vault]

req_D2KX9W1pf8KChk

[vernal heath]

Well that payment failed so there was no invoice generated

[wraith vault]

but in the event you can see it is charging $71.88

[vernal heath]

You're applying prorations though, so we apply credit for unused time on the 6 seats and then bill for the remaining time in the period for 8 seats

If you want to charge the full amount for the upgrade then pass proation_behavior: 'none': https://docs.stripe.com/billing/subscriptions/prorations#disable-prorations

[wraith vault]

but the customer has already paid for 6 seats and now he wants to update to 8 seats so he should be charged for only those 2 seats

the main problem it is charging for whole 8 seats

[wraith vault]

@vernal heath update on this

[vernal heath]

Please be patient, we're helping other users too

Also, please don't @ me

There's no easy way to only charge for the net amount of new seats (2) in an upgrade call really

[dusk violet]

Hey! Taking over for my colleague. Let me catch up.

[wraith vault]

but why will the user pay for whole 8 seats, I think without prorate change we cannot update the user seats as this could occur in the halfway of the billing period

@dusk violet are you working on this?

[dusk violet]

Yes checking...

[dusk violet]

The invoice contains the remaining period and the new period

Also if possible to share the successfull request Id of the update

[wraith vault]

adding this screenshot for your reference

[wraith vault]

req_q3WZHkngLawvSv

[dusk violet]

So yes this is exepcted, as you specified no proration when updating the invoice..

[wraith vault]

proration is specified there

[dusk violet]

That setting if for dashboard updates. Also proration aren't a mode, it need to be specified for each update

Here your backend for example did specifies the proration behavior to always_invoice
req_q3WZHkngLawvSv

[subtle mauve]

Hi, I’m stepping in on behalf of my team member to discuss this issue.

Please read the following carefully, as there seems to be some confusion regarding our query and your understanding:

Use Case:

• A user subscribes for 6 seats on the 1st of the month. On the 15th, the user wants to add 2 additional seats, bringing the total to 8 seats.

In this scenario, if we opt for immediate proration, the user should only be charged for the 2 new seats for the remaining 15 days of the billing cycle. Alternatively, we could choose to charge for these additional seats in the next billing cycle. We also have the option to reset the billing as per the stripe features for subscription.

Problem:
Ideally, the user should not be charged for all 8 seats since they have already paid for the initial 6 seats. The issue we are facing is that they are being charged for all 8 seats without any adjustment for the amount already paid. Let me know if you need any further clarification on the use case!

[dusk violet]

Thank for the additional details.

The issue we are facing is that they are being charged for all 8 seats without any adjustment for the amount already paid
According to this requestId req_q3WZHkngLawvSv you are specifying a Coupon zhicqPmn with 54$, that's why there was no adjustment on the previous 6 seats.

[subtle mauve]

Yes, correct user has applied coupon discounts to purchase the first 6 seats, so how should we handle this situation?

As we would only like to charge for the newly added seats based on proration.

[dusk violet]

The proration works on the period of usage and not of seats (which is the same after all)

[subtle mauve]

I can see the metadata for creditAmount

[dusk violet]

In the invoice you are referring to, the preivous line item (6 seats) is considered 0$ as there is a coupon. The new line_item will have the prorated amount for 8 seats.

[dusk violet]

Stripe don't manage/handle the metadata datas, these are values set by your integration/backend.

[subtle mauve]

understood

[subtle mauve]

How should we handle this use case? So, that stripe should consider this, as user can't select for just 2 seats, right? As it will downgrade the no. of seats and user need to purchase 2 new seats and we would like to charge just for that 2 new seats.

[dusk violet]

Previously you said that the update occurs on the 15 of the month. The main ask here is: For the remaining period (15->30) you want to charge the customer for 2 seats or for 8 seats ?

[subtle mauve]

As they are subscribing on the 15th day of the month for 2 new seats then, we should only charge for 2 new seats.

[dusk violet]

Then you need to make an update for 2 seats and not 8

[subtle mauve]

Will it not downgrade the no. of total seats from 6 to 2 seats as this is an update?

[vernal heath]

How you think proration works is not actually how proration works unfortunately. We don't prorate according to the difference in quantity (i.e. charge for 2 seats when you downgrade form 8 to 6). We prorate according to time remaining in period and calculate a unused time for the 8 seats and remaining time on 6

If you want to handle downgrades differently, then you're going to need to do that manually

[subtle mauve]

you've misunderstood our use case, plz. read carefully.

Initially, when the user applied a coupon while subscribing for 6 seats, the total purchase amount became $0. Now, when the user attempts to subscribe for 2 additional seats, Stripe is charging for all 8 users because the initial subscription for 6 seats had a purchase value of $0. How can we resolve this so that Stripe only charges for the 2 newly added seats?

or should we go with trial method instead of coupons for subscription plans, in case coupons is not the suitable way to handle this kinda situation?

[vernal heath]

I think we've already answered that – you can't. Because of the proration calculation we discard the original discount unfortunately: https://docs.stripe.com/billing/subscriptions/prorations#prorations-and-discounts

[subtle mauve]

Understood, so we will proceed with the trial period. However, do we need to manage the data on our end? For example, if we offer a 30-day trial and a user subscribes for 6 seats, then decides to add 2 new seats on the 15th of the month, will Stripe automatically apply the trial to those 2 new seats for the remaining 15 days?

[vernal heath]

Are you applying a trial via a discount?

[subtle mauve]

Not exactly. We were initially considering applying a discount, but since it doesn't meet our requirements due to Stripe's constraints, we are thinking about utilizing the trial feature for subscriptions. However, I see one challenge that I mentioned earlier.

we're thinking to apply trials from subscriptions feature itself. Is it possible to apply trials through discounts as well?

[vernal heath]

No

I was just confused because you mentioned 30-day trial but then there was a 100% off coupon the sub you shared

For example, if we offer a 30-day trial and a user subscribes for 6 seats, then decides to add 2 new seats on the 15th of the month, will Stripe automatically apply the trial to those 2 new seats for the remaining 15 days?
You can configure that on an API call basis via trial_end: 'now'. I think the default would be to continue trialing

[subtle mauve]

Noted, we tested just now, it solves our problem. Thanks for answering promptly.

[vernal heath]

Perfect!