marvi

[humble zenith]

So for (1): I would recommend listening for payment_intent.succeeded in order to update DB entries related to the Payment Intent: https://stripe.com/docs/api/events/types#event_types-payment_intent.succeeded

For (2), I'm not sure I follow. The customer will always be returned to the success_url specified on the Checkout Session if payment is successful, so that has nothing to do with webhooks

[junior rose]

It appears that I didn't explain it very well for (1) so let me try again.

1. I "transport data" betwen /create-checkout-session and /webhook by storing them in a table
2. I listen for "chekout.session.completed" to get the payment_intent and store it where the checkout session ID matches
3. I listen for "payment_intent.succeded" to store the entries in my main table where payment_intent matches
4. I delete the data in the table that I used to transport
   sometimes checkout.session.completed comes after payment_intent.succeded and my method fails to store the data

Thanks for (2)

[eager sparrow]

Hi there. Taking over for two-shoes as they have to step out

Give me a bit to catch up on context

Yeah so our events aren't guaranteed to come in any sort of order: https://stripe.com/docs/webhooks/best-practices#event-ordering. So, you'll have to rethink your approach to this a bit where you don't rely on an order for the events

[junior rose]

Is there anything that references checkour session object and event
payment succeded

Like how can i know which checkout session corresponds to which event

[eager sparrow]

https://stripe.com/docs/payments/checkout/fulfill-orders#handle-the-event

checkout session completed event already indicates a successful payment

and correlates the session to the payment

[junior rose]

So basically I can in use it instead of payment_intent.succeded?

[eager sparrow]

Yeah

[junior rose]

Thanks very much!