#zlf_api
steel topazBOT
👋 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/1399933228600791151
📝 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.
- zlf_api, 1 day ago, 57 messages
split vortex
We encountered an issue when using a Stripe coupon.
We have a coupon with a value of $24.99, and there are two products involved:
Product A: $24.99
Product B: $14.99
Case 1:
When we create a subscription with both Product A and Product B and apply the coupon, then later update the subscription to add another Product B, Stripe charges $14.99 + $14.99 during the proration.
Case 2:
When we create the same subscription with Product A and Product B, but without a coupon, and then add another Product B later, Stripe charges only $14.99, which is expected.
Both updates are made during the active billing period, and proration is enabled.
The second behavior is expected, but the first one is not — we only want to charge the customer for the newly added Product B ($14.99), not duplicate charges.
Can you help clarify why this happens when a coupon is applied, and how we can avoid this double charge behavior?
echo mantle
Hi there, what's the subscription ID?
split vortex
Case 1:sub_1RpkovHiYvn8ZIkePSOuGXUQ
I reproduced this problem in a test environment
echo mantle
Ok, let me take a look
echo mantle
in_1RpkowHiYvn8ZIke7DgosWhS is the first invoice that sub_1RpkovHiYvn8ZIkePSOuGXUQ generated, its amount is just 14.99 USD, not $14.99 + $14.99 as you described.
Am I looking at the correct subscription?
split vortex
Maybe I didn't explain it clearly. What I'm doing is: when modifying the subscription, I use the invoices/upcoming API to add a $14.99 product to preview the price, and I see that the amount to be paid is $14.99 + $14.99.
echo mantle
Can you share with me the ID of the request that you created to preview the upcoming invoice?
split vortex
This is the request ID from the previous test: req 5RBQuOFe9NsQ0O
This is the request ID just tested: req g9ztiKNvOoooKI
echo mantle
Can you also share with me the full repsonse since Stripe doesn't log GET response
split vortex
echo mantle
Thanks. let me see if I can reproduce it
Ok, here's what happened, you created a subscription on 2025-07-28 06:46:01, and one hour later at 2025-07-28 08:33:06 UTC you create a GET request to preview the upcoming invoice with subscription_proration_behavior: "always_invoice", and price B quantity to 2.
split vortex
yes
I'm a tester, but for users, they can modify their subscriptions at any time during the cycle
echo mantle
Ok, let me run a few more tests. one sec
split vortex
When creating the subscription, I used both Price A and Price B. Later, when modifying the subscription, I increased the quantity of Price B to 2 — essentially adding one more unit of Price B. So the invoice should only charge for one additional Price B, not for two Price Bs in total.
This issue only occurs when I create the subscription using a coupon. However, when I don’t use a coupon and follow the same process — first creating the subscription with Price A and Price B, then updating the quantity of Price B to 2 via the upcoming invoice — the result is that only one additional Price B is charged.
echo mantle
Yes I can reproduce the same and it doesn't look right to me. I'd report this problem to the Stripe billing team
split vortex
Could you please take a look at this request: req_r3rmkNsv3FMsr5? This is the second case I mentioned (without using a coupon), and the calculated price is as expected.
I reported this issue a couple of days ago, and they asked me to create a DM. However, the creator of this test account has already left the company, so I can’t receive any email feedback. That’s why I’m raising this issue here again, hoping it can be resolved.
echo mantle
I see, let me see if this problem is already reported
split vortex
Alright, thanks for checking.
echo mantle
I've already reported this issue to the billing team. If you want to follow up on it. Use the link that sent to your DM to create a support ticket
steel topazBOT
Hello @split vortex, we have sent you a direct message, please check it at https://discord.com/channels/@me/1399328788260585583
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
echo mantle
Sure thing
split vortex
I have successfully created it and received the message in my email. Am I now waiting for you to contact me
echo mantle
Thanks. We will respond to you through emails