#altairsama2_webhooks

1 messages ¡ Page 1 of 1 (latest)

thorn steepleBOT
#

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

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

rotund flume
#

Stripe doesn't guarantee that customer will only be redirected to your URL after receiving 200 status code of the events

dusty sable
#

so even if dont return any response to webhooks, it will still be redirected?

#

even a 403 or a 500 will suffice as long we get webhooks before user is redirected

#

otherwise it's a major issue for reconciliation

rotund flume
#

so even if dont return any response to webhooks, it will still be redirected?
Yes! Customer will still be redirected to your URL even if your server doesn't respond to the webhook events

dusty sable
#

and if so, are there any suggestions for reconciliation UX?

rotund flume
#

Stripe will wait for 10 seconds for your checkout.session.completed event to respond 200. If 10 seconds is hit, Stripe will proceed with the redirection regardless whether your server responds to the event.

In summary, redirection to the success_url can be earlier if your server responds faster to checkout.session.completed event, but Stripe will still redirect after 10 seconds if no response is returned.

and if so, are there any suggestions for reconciliation UX?
If your database hasn't updated to the latest payment details, I'd recommend showing the payment is still processing. They will receive a separate confirmation email later.

Alternatively, you can set the success_url to the interim URL with "Payment processing" and perform another redirection again to the payment outcome page.

dusty sable
#

thanks! appreciate it, 10 seconds should be enough for us

rotund flume
#

I'd recommend testing this in test mode to ensure that this meets your requirements

dusty sable