#jumptimesthree_best-practices
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/1240010636860194816
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! Yes, you must use webhooks if you're not handling fulfillment manually (e.g., by looking at purchases in the Dashboard and fulfilling them by hand).
I see. From my understanding of how checkout works, if the payment is successful, the user will be redirected to the success_url. Would it not be a good practice to then have automated fulfillment driven by the loading of the success_url?
Yes, you can do that, but people can pay successfully and never land on the success_url.
Best practice is to have both webhooks and the success_url trigger fulfillment, with the first one that happens triggering fulfillment, and the second one being a noop.
Understood. This was helpful, thank you!
Happy to help!
For the case where people pay successfully and never land on the success_url - you're mainly talking about edge case conditions like a network blip or them prematurely closing out the browser, right? This will not happen most of the time in the typical case?
It happens more than you'd think, but yes.
We are expecting pretty low volume for the foreseeable future, so I'm just wondering if a fallback to manual fulfillment would be reasonable for those cases
In those cases the only way to know you got paid would be webhooks, or looking in the Dashboard and reconciling manually.
If your volume is low enough it might be feasible, but webhooks are the recommended approach.
makes sense