#rstupek
1 messages · Page 1 of 1 (latest)
Hello
Hi
There isn't really documentation or a guarantee of the specifics here since a lot of it relies on financial partners.
What are you really trying to figure out?
I'm trying to understand how long I need to keep order data on a server to account for completing the order in instances where the customer isn't directed back to the url provided in the payment intent
You mean how long to keep data in your database?
we don't keep that data in a database... when the customer gets to the payment portion of checkout, completes their purchase on stripe but doesn't get sent back to the url, what conditions would cause that and how long might it take for a webhook to get called for that
If the customer loses connection or closes their browser after clicking the "pay" button but before the redirect then the purchase can be completed without them hitting the return_url. Regardless you will still receive the Webhook on your server and when that happens your Webhook handler should trigger your fulfillment process.
is there any significant delay in that webhook being called, are there specific payment types which would yield long delays for payment_intent.succeeded
Have you taken a read through https://stripe.com/docs/payments/checkout/fulfill-orders ?
That talks about delayed notification methods which you will want checkout.session.async_payment_succeeded for
In terms of how long it takes for a webhook to arrive, it should take only a few seconds.
But we don't guarantee that as it can depend on a variety of factors.
naturally but you wouldn't expect it to be hours for it to arrive right
not that I'm seeing that
Correct, it should not be hours
checkout.session.async_payment_succeeded can take a while though? days?
Yes
Bank debits for instance take 3-5 business days
If you click on the specific payment method type in our docs you can see information about how long it can take
ok that's what I thought and you can test those payment type scenarios as well?