johnm_api

[pseudo sparrow]

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

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

[urban echo]

hello! fyi i'm juggling a few threads atm and it might be a bit before i can get back to you, but i'll take a look at this asap

[dusty marten]

Thanks @urban echo

Here is a screenshot of the invoice in question

This was discovered by a tester, it has not happened for us with any real users yet.

When coupons were on customers and not subscriptions the invoice would be "Unused time on 4 seats: -$432" and "Remaining time on 5 seats : $540" Resulting in net: $108 with 50% discount = $54 charge.
I'm trying to get the same functionality while also complying with new Stripe changes.
Any help you have would be greatly appreciated

[urban echo]

ok sorry about the delay, i'm looking into this now!

which API version were you on before? and is there any chance you have an invoice where you tested this same thing on that prior API version?

it looks like this one is being done on 2022-08-01?

[dusty marten]

We were on 2022-08-01 and now moving to latest one 2025-12-15.clover
I don't think I have an invoice showing previous functionality but I could probably roll back and generate one

This is an invoice from another test account using the latest API version displaying the same issue - https://dashboard.stripe.com/acct_1JaiWTDqY7XgZmx0/test/invoices/in_1SpSOJDqY7XgZmx0F1fhUv4i

[urban echo]

i'm a little confused because the invoice you shared was also created and paid with 2022-08-01

are you saying that you're seeing the new functionality regardless of what version you're using to create and pay the invoice?

[dusty marten]

I think that one was created with the later version, Request ID: req_DEZYfsirnLyEdC

But I think the issue is actually associated with now having to have coupons on subscriptions rather than customers.
We can no longer have coupons on customers and must use the subscriptions. This results in different proration behaviour.
Maybe there is something we can do to have the same behaviour we used to have on customers.

Is it a common problem to have a subscription, add a coupon half way through, upgrade the subscription and have a negative invoice? Maybe our usage pattern is wrong?

[tough olive]

Hi there! Sorry for the delay; I'll be taking over for solanum here

Just getting caught up and I'll dig in here

So your overall goal is "how should I apply a discount to an existing Subscription without generating a negative proration Invoice?"

Also the Invoice you supplied (in_1SpSVSJEEuL0FeY0p809BYAm) isn't a cycle Invoice - its a one-off that you created explicitly. Could you explain how that fits in?