#didico_webhooks-timings
half streamBOT
đ 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/1301563094798958667
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
unkempt gyro
Here you can see that the event was created 3:37:05 PM CET, but only sent at 3:37:24 PM CET
scenic torrent
Yeah that's not abnormal
In terms of how to handle this on the frontend, it depends on your integration
But your current approach doesn't seem too bad to me
unkempt gyro
Yea, the problem is that this approach doesn't work on all browser, as some of them might block cookies by default or by extensions
We have a frontend that's on nextjs, and some microsservices in go (where the webhook lays on), so we just make the user as a paying one (activeLicense property), when the event is received, and frontend checks that activeLicense property to remove the paywall.
unkempt gyro
Checkout
scenic torrent
So you can configure checkout to pass checkout session id in success_url: https://docs.stripe.com/payments/checkout/custom-success-page?payment-ui=stripe-hosted#modify-the-success-url
You could then pass that checkout session id to your backend and check via stripe api that customer paid and mark them as active
Just another suggestion
unkempt gyro
Makes sense, I'll try some of the alternatives and let you guys know if there's something else
Thanks!
scenic torrent
No problem
half streamBOT