ashish_best-practices

[stray geyser]

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• ashish_api, 57 minutes ago, 13 messages

[finite cloak]

Just to add on, the guide makes a request to retrieve the session object, but I feel that if someone maliciously refreshes the page multiple times, I'd get rate limited or blocked from stripe. Do I handle this myself or encrypt and append the discord user data in the return_url parameter?

[swift drift]

hi, Stripe rate limits are pretty generous, but if you were truly concerned about this you could handle rate limiting on your side, or save the session info and redisplay when the user returns. Checkout Sessions also expire after 24 hours, so you would only need to be concerned for that long

[finite cloak]

Ah that's interesting, I didn't know checkout sessions were temporary only.

One more question, if a payment fails, would stripe still redirect the customer?