#mboras_api

1 messages · Page 1 of 1 (latest)

short kilnBOT
#

👋 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/1219240921586208808

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

chrome remnantBOT
tired stirrup
#

I am thinking loud now.

This will be problem since I am handling subscriptions?

#

I need customer ID for each email that I am sending?

severe delta
#

You don't need one - Checkout will generate one if you don't provide one. But if the email address maps to an existing cus_xxx in your database/system then you should re-use that yes

#

To answer your original Q, you'd likely have to build an endpoint that the email links to that generates the session and passing the discount and other parameters as required

tired stirrup
#

yeah

#

some users are existing

#

some will be new because I have re-released app with payment

#

some of them haven't come since then and they're not strripe customers yet

severe delta
#

Then you'd need some logic in your application to handle that (if they're existing, pass customer parameter when you create the session. Otherwise omit it)

tired stirrup
#

ok

#

I'll probably redirect users from email to my app with some query parametres and handle all of that

#

thanks

severe delta
#

Sounds good!

tired stirrup
#

tnx