#samyak_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1308761298246438912
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
There is not no. The recommendation is for you to persist the cus_xxx internally that maps to a user ID/sessiona and re-use that when creating session/payments for them
Checkout will create a new customer if needed when you don't provide one, and we don't prevent multiple customers with the same email
yeah i agree about persisting the cus_xxx internal mapping, but we are allowing the customers to purchase without logging in, so we don't have a way to do internal mapping in this. Is there any other way to avoid this issue ?
There is not I'm afraid
okay, thanks