#kennyjack_api
small forumBOT
👋 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/1424689721648480286
📝 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.
- kennyjack_api, 4 days ago, 39 messages
- kennyjack_api, 4 days ago, 9 messages
- kennyjack_api, 4 days ago, 40 messages
strong elm
FYI, here is the response return from stripe
This is my subscription ID sub_1SFAPrArTeYcLw6yvVhCIeW6
scenic osprey
👋 Hi there. Let me take a look
The subscription here was created with two different prices, and a discount that applies to the entire subscription. Is this the correct example?
i.e. I don't see an update that was made to add another item
strong elm
Yes, can refer this first request req_BB39ocwyj5okwp
It applied 50% discount on all item before try to update on second request req_gzGuBUcTLSJXr4
The second request that was made to add another item will not applied any discount
small forumBOT
scenic osprey
From the reply you supplied, the discount doesn't appear to be applied to the item with quantity: 2
strong elm
let me rephrase my sentence
Yes, but Stripe won’t know from the first request that the item already had a 50% discount applied, and that the user has completed payment and the subscription has been created. However, on the second request with quantity set to 2, Stripe shouldn’t reapply or backcharge the discount that was already accounted for in the first request, right?
scenic osprey
You're previewing an invoice with the current date, so you're seeing prorations.
If you supply the date of the next billing cycle, then you should be able to see what will be charged at that date: https://docs.stripe.com/api/invoices/upcoming?api-version=2024-06-20#upcoming_invoice-subscription_proration_date
next echo
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!
small forumBOT
strong elm
Sure, i'm testing now with Arran's suggestion
umbral lynx
@scenic osprey I tried to contact you in DM, can you please check?
small forumBOT
@umbral lynx looks like you're in the wrong place, this thread is for someone else's question.
- If you have your own thread please chat there.
- If you have a question or a followup to a closed thread use one of the buttons in https://discord.com/channels/841573134531821608/842637025524842496 to get help (we don't reopen closed threads).
Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.
strong elm
This is my request ID req_OXS72smi5hX6wb, i try set current timestamp in the subscription_proration_date field. But i still get the same response
strong elm
my desired outcome that should only charged the quantity 1 of price_1S7WO3ArTeYcLw6yjT7l4NVv item . Because previously the item price_1S7WO3ArTeYcLw6yjT7l4NVv was purchase with 50% discount it should not reapply or backcharge the discount that was already accounted for in the first request
next echo
Yeah unfortunately our billing system does not work that way. We'll always invoice for the quantity on the sub item at the time of the invoice generation, regardless of whether something was previously paid or not
If that is not desirable, you'd need to apply a negative invoice item manually to deduct the previously paid amount
strong elm
I see, is there any other way like another API, flag or something else that can help resolve my problem?
Other than apply a negative invoice item manually to deduct the previously paid amount
next echo
How can I ensure that the 50% discount on the original item A isn’t applied when purchasing the additional item A?
'Item A' beingprice_1S7WO3ArTeYcLw6yjT7l4NVv?
strong elm
Yes
next echo
No other way that I can think of, no. The discount applies to all relevant items as it is/was top-level
But you've removed the discount now? https://dashboard.stripe.com/test/logs/req_fJVqZPz86NqMIn
next echo
Nevermind, ignore me
The discount was one-time, so it shouldn't apply to the next/upcoming invoice at all
strong elm
Ok, Thanks for your time.