#supreeth_20471
1 messages · Page 1 of 1 (latest)
Hello supreeth_20471, we'll be with you shortly! 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.
• supreeth_20471, 3 days ago, 10 messages
• supreeth_20471, 3 days ago, 16 messages
• supreeth_20471, 4 days ago, 8 messages
• supreeth_20471, 6 days ago, 7 messages
• supreeth_20471, 6 days ago, 4 messages
Hello! Can you give me the request ID showing the error you mentioned? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
req_exeMRYchOSl0DA
To clarify, this Customer already has a Subscription and you want to increase the quantity of one of the existing line items? Or are you trying to add a brand new line item to the Subscription?
tbh im not sure how to go about this. let me give you a bit more context. think about slack's pricing model. you get charged for the number of active users on your platform. so when a user creates a workspace they start with one unit and i create a subscription with quantity one. what i was doing till now
--> when new users get added i update the subscription quantity directly (But this kind of messes up the invoice)
what i tried doing
--> instead of updating the quantity directly in the subscription, i thought of adding a line item for better reporting in the invoice.
im not sure if this method even makes sense tbh.
Could you tell me which method of the above 2 are preffered. or if there's a totally different way this can be handled?
👋 hopping in here - you mentioned that when you tried to update the sub quantity directly it messed up the invoice. Can you give me more details on how specifically it messed up the invoice?
From what you've described, updating the subscription quantity is what I would've suggested so I'm surprised to hear it's not working as intended
it is def working as intended. the math is perfect. its just the way its show on the invoice. this thread has more info on the invoive issue https://discord.com/channels/841573134531821608/1163904245960036404
Ah I see - you were hoping for a different invoice item description than what we offer (but the math works fine)
so for every new customer added it adds 2 line
i.e -> one for the refund
i.e -> one for the new charge
so lets say 250 users get onboarded in a month > the invoice would have like 500 lines which is not ideal
yes and is this the best way to go about it? we can also build our own invoice but just checking into to see if we are using the api right?
If you're intending to build your own invoice items then you're not using the Invoice Items API correctly. Currently, you're passing in the recurring price ID you used to create the Subscriptoin, which won't work because Invoice Item creation requires you to use a one-time price. To get this to work, you'd have to calculate how much you'll want to be charging for that Invoice Item yourself and either creating a new one-time Price for it, or passing in amount and currency with the Invoice Items API directly
🤔 im not sure i get that. the workspace does stay on a recurring plan but the quantity changes. how would that be a one time price?. lets say the customer goes from 5->6 users. the next billing cycle they need to be charged for 6 units. im not sure how a one time price would work 🤔
Let me clarify - if you're intending to create the Invoice Items yourself then it's completely separate from the Subscription and you can't reuse those prices at all. Invoice Items that you create directly cannot be created with recurring prices - you would have to do all those calculations/prorations yourself and then create a one-off Invoice Item for that price. It wouldn't be linked to the specific subscription/recurring price