#megan-gavette_api
brave zodiacBOT
👋 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/1278366122910941266
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
balmy meteor
Hello, happy to help but I am not quite clear on what this question means in Stripe terms. Can you give a specific example of what some of these product codes might look like and go in to a bit more detail on how they are used here?
delicate mulch
Hi there! Absolutely. Give me a minute to write everything out
So this is an AirBnB type site for military travelers. For users trying to list properties they want each user to pay the same amount per property. So a 1:1 subscription model. We built a custom site on either MERN/LARAVAL ( I am confirming) and are going to be integrating the Stripe API. Team looked into configuring it the way the client requested, and there are concerns that in order for it to be 1:1 it would have to create indivual product codes per property for each user, which would mean that when invoiced/money billed from their accounts it would charge per individual product code as opposed to one lump sum on their account. Which for obvious reasons is not ideal. How do we give the client what they want without an admin headache on the back end
Sorry it was built on Next.js
balmy meteor
Gotcha, getting closer but I am still a bit fuzzy. When you are talking about product codes are we talking about whether or not to make individual product objects for each property? Or something else? https://docs.stripe.com/api/products
Are your users basically subscribing to a property or properties for the length of their stay?
Not quite sure if I understand the lump sum part either but our subscriptions do combine the various products on them in to single charges. So if you have a $500 monthly price and a $250 monthly price on a subscription, we would charge $750 once a month and you can even add other one time fees that get added to the next monthly charge when that happens.
I feel like that may still be fairly off base from what you described. Can you give me an example of how you would ideally like to charge a customer on your platform and an example of the type of charging that you want to avoid?
delicate mulch
yes that is what I am trying to figure out. my team is suggesting that this is not a possible function. that each item would be billed separately and their bank acocount would reflect multiple charges rather than one inclusive charge for the entire month
balmy meteor
Gotcha, we do charge one time for all of the items on a subscription. Basically for our standard subscriptions, when you create the subscription you specify a number of subscription items which are prices that we will charge on a recurring basis. There are some restrictions like that you can't have a monthly price and yearly price on the same subscription (though there is a workaround for that if you need it), but we do charge for those items by creating a single invoice that sums up all of the subscription items and one time charges and make one charge on the customer's payment method for that.
https://docs.stripe.com/api/subscriptions/object#subscription_object-items
https://docs.stripe.com/billing/subscriptions/overview
delicate mulch
And are there any challenges with getting this to function with a Next.js build?
balmy meteor
Not that I'm aware of. Our API is just a REST API, so we don't really know what your backend is, we just know the data that it sends us
delicate mulch
got it
and just to confirm, within this model a user could have 100 of the same item (different product codes of course) and each month it should consolidate all of into one invoice
balmy meteor
Our subscriptions have a restrction of 20 items per subscription. If you need 100 you I'd reccommend reaching out to our support team and explain your use-case and they may be able to help you there. Do you regularly have subscriptions with that many items or more? https://support.stripe.com/?contact=true
delicate mulch
this will be very common for our client. they already have a cache of users confirmed who will have 100+ properties to list on their site
balmy meteor
Gotcha, unfortunately we don't have a great way of handling that at the moment. As mentioned our support team may be able to help you have more items per subscription, but that would still likely require you to break up items across subscriptions if each properly mapped to one subscription item in Stripe, which would mean multiple charges.
That being said, you don't necessarily have to make this a 1:1 mapping. I have talked to users that have their own mapping of what things one of our subscriptions is paying for and generate their own invoices to send to their users to break the charge down properly.
brave zodiacBOT
delicate mulch
so I offered this to my client and they want to be as hands off as is possible for this. They do not want to be creating custome contracts for clients becuase this would be a large undertaking as most of their client have a large number of properties to list.
But just to confirm each user will have 1 subscription per property. They don't want to have 1 subscriptions handling multiple properties. So when it comes to invoicing is there a restriction on how many items can be on an invoice?
balmy meteor
Ah, 1 subscription per property would result in one charge per property. We don't have a way to combine charges across subscriptions unfortunately. For situations like this we definitely would recommend consolidating these to as few subscriptions as possible. Will this client be managing things directly through their Stripe dashboard? If not, you could abstract that mapping away from them. Otherwise it may make sense to just break things up in to bundles of the largest amount of subscription items available to you
delicate mulch
this is what I was afraid of. Now within 1 subscription is there a way to ensure that each property get charged the same amount. So for instance
1 property = $10
5 properties = $50
10 properties = $100
an so on? This way at the very least there is no concern for clients to be upset that the pricing is not the same across the board?
and it would be within the same subscription uo to 20 properties.
willow wagon
Hi there 👋 taking over, as my colleague needs to step away
Give me a few minutes to get caught up.