#jonwaldstein
1 messages · Page 1 of 1 (latest)
Yeah I would rely on webhooks here not the callback from the front-end. There are some payment methods that succeed asynchronously. Furthermore, even for PMs like Cards where you hear back immediately, there could be some sort of network issue or browser/device crash. Webhooks are the most robust way to handle the updates in your DB
You can see all the payment intent webhook events that are available to be listened to here: https://stripe.com/docs/api/events/types
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Okay thanks. Out of curiosity, what actually triggers stripe to navigate to the return_url? I would imagine some kind of successful status
Just the customer successfully submitting payment details
But as I mentioned, there's not a guarantee they'll reach that url, so it's not recommended to build logic around it that's critical
ah okay, good to know - thanksQ
No problem