#vlady-_best-practices
1 messages ¡ Page 1 of 1 (latest)
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.
- vlady-_code, 1 hour ago, 11 messages
đ 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/1240002713534595164
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! Have a look here: https://docs.stripe.com/payments/checkout/fulfill-orders
Oh, great! Thanks Rubeus, but would this still be available in my case?
The webpage and the server are different servers/processes, am I able to send the checkout session from webpage and process it on the backend separate server?
You can add the Checkout Session ID to your success_url and then, when someone lands on that URL, you can grab the Checkout Session ID from the URL, retrieve the Checkout Session from the API, check to see if it's been paid or not, then do whatever you want from there: https://docs.stripe.com/payments/checkout/custom-success-page
Got it!
Thanks a lot!
Note that people can pay you without ever landing on your success_url, so you can't rely on that happening every time.
It's more of a fallback for the webhooks approach, not a replacement for it.
Oh? Well, what can I do in this case?
You use the webhooks as the primary way you fullfill, with the success_url approach as a fallback.