#bungee_docs
raven tartanBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1250755411519344640
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
river briar
hi! they would be eligible yes, if you don't want them to be you'd need to implement the controls on your side
for example collect email addresses in your own site instead of Checkout(and then create a Customer and pass it to customer on the CheckoutSession API) and then you can implement a uniqueness constraint on people signing up, or handle the checkout.session.completed webhook and cancel subscriptions where you detect duplicates and contact the user explaining
hushed summit
Hi! what's the recommended approach you'd recommend here? any of the ones you suggested?
Like, what would be the best practice to handle this situation? 🤔
river briar
I would say either approach works, the difference is in preventing the sign up at the cost of more complexity/an extra auth step on your site, versus cleaning up 'wrongly-created' subs, at the cost of confusing ux