#wee_code
hybrid knotBOT
đ 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/1329896889876742165
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hard cave
Hi, have you already enabled the functionality to limit the customer to one subscription? If not, we document this here: https://docs.stripe.com/payments/checkout/pricing-table#limit-subscriptions
We add more details as to how to achieve it here: https://docs.stripe.com/payments/checkout/limit-subscriptions
night maple
Hey! Yes, and the issue is not customers having multiple subcsriptions. The problem is different. Basically, after a user signs up into our Platform for the first time, we also create a stripe customer for them. Then, they are directed to the pricing table since they dont have any prior subscriptions as their new customers. We create the customer session in our backend, and the Frontend appends the client secret to the pricing table. To my understanding, shouldnt this now make it so that when the customer subscribes, it Should use the customer already made for them, instead of creating a new one since we pass the client secret to the table? However, right now, stripe still creates a new customer none the less and the subscription goes to that new customer, not the one we want
hard cave
Ah, we document how you can pass the existing customer, https://docs.stripe.com/payments/checkout/pricing-table#customer-session. After you create the customer, you can pass the customer id on the customer session.