#will_best-practices
ebon siloBOT
đ 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/1342341925717413908
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
stark sapphire
I was thinking i could try looking at all old subscriptions when a new customer is created and then having code move it to the old customer
You would want to collect the email first, then perform this logic check before accepting their key-in new payment method
bronze spire
I would much rather have it be one step to streamline the payment process as much as possible. Something that would be reasonable is if I could do the following: in the stripe checkout page when limiting to one customer, right after the email is entered and before the user makes it to the rest of the info, it must be performing some sort of search for non-canceled subscriptions with the given email. If I could build on top of that to also perform a search for canceled subscriptions, that would work. But if that isnt possible, and nothing like that is possible, it seems like our only option might be to either process after the fact (although it seems like you can't really move a subscription from one customer to another or even delete it and make a new one on the correct customer because the payment method would've already been used at that point). If there aren't any options like that, is there a way we can collect the email first and then not require them to enter it again in the checkout page if we're using the embedded checkout?
stark sapphire
Yeah I totally get what you are describing, but I don't think we have such a abstracted API. Sorry if it's not the answer you are looking for.
It's back to you need to (and have the flexibility to control) the customer managing system.
bronze spire
So are you thinking that the best we'd be able to get is this: anyone wanting to subscribe must enter their email, then we do a search to identify if they've had a previous subscription. We set the customer id like this "sessionParams.customer = customerId;" if they had a previous subscription. Then it takes them to the checkout session where they need to enter their email again along with all the billing info. Is there a way to avoid them entering the email twice?
stark sapphire
When you are reusing a Customer, I think the Checkout Session wouldn't ask for an email again. Do you see otherwise? Happy to look at a specific Checkout Session Id