#phezyn_best-practices
limpid lodgeBOT
đ 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/1397584392607633493
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
gusty wolf
Why do you need to create a different price for each user?
median hatch
Because I want the user to be able to set whatever price they want for the subscription
From what I understand the only way for the user to be able to choose the exact price they want to pay, they have to be the ones to create the price object
I have seen people recommend creating an array of price objects for the integers 1-100 to encompass most of what people are likely to select to pay
What do you think?
gusty wolf
If this is going to be on the fly, I recommend passing an amount to checkout instead of creating a price object each time
median hatch
From what I've read previously if you want to create a subscription you have to use a price object, is that not the case? Can I create a subscription and pass in an amount?
gusty wolf
You can
median hatch
Oh cool, so in this manner I wouldn't create a price object at all. Is there any functionality I may lose out on by not having a price object involved in the checkout?
gusty wolf
Other than price reusability, no
median hatch
So the subscriptions on our platform are not toward our organization, they are being sent to other entities connected stripe accounts and we're taking a % fee from that transaction. All of that is still possible without a price object?