#BrianC - Checkout
1 messages · Page 1 of 1 (latest)
Hello! Yep, that's not only possible, but is how the system is designed to work...
Let me find the docs, one sec...
Look at the callout on the right here: https://stripe.com/docs/payments/checkout/fulfill-orders#testing-end-to-end
Aha! that is news to us. Thankyou!!
Just to be sure we are reading this correctly:
"Your webhook endpoint redirects your customer to the success_urlwhen you acknowledge you received the event. In scenarios where your endpoint is down or the event isn’t acknowledged properly, your handler redirects the customer to the success_url 10 seconds after a successful payment."
This is saying that the redirect to the success URL with appended session id happens after the webhook endpoint is sent and an answer is received back to Stripe (success or otherwise). Is this correct?
Mostly, except that last bit where you say "success or otherwise". We redirect after receiving a successful response from your Webhook Endpoint URL or when 10 seconds have elapsed.
"Otherwise" does not factor into it.
I see. I thought it was the other way around. Good to know. I thought the success URL happened immediately and the webhook was delayed.
One last question - I don't see it in the docs and I'm pretty sure there is not, but is there a way to set a URL for each scenario - received response (one URL) waited 10 seconds (another URL)?
Regarding your first response above, the idea is that we want to wait for your server to receive the Checkout Event before redirecting because it gives you a chance to do things like grant access to paid features and whatnot on your end before the redirect happens. That way the customer landing on your page can immediately see/access what they paid for.
I don't think I understand your last question, can you provide more details?