#cavani-pi-charge-events

1 messages · Page 1 of 1 (latest)

fickle sinew
#

Hey there!

ionic carbon
#

Hi

#

🙂

fickle sinew
#

When using Payment Intents you can likely expect both charge.succeeded & payment_intent.succeeded events for successful payments

#

Think of the Payment Intent of a state machine that facilitates the actual payment (the Charge)

ionic carbon
#

So payment intent can have many charge objects but only one successful charge right?

#

And so when the payment intent gets the successful charge the charge.succeeded event also gets fired?

#

Basically my app currently used payment intents however for the webhook it listens for charge.succeeded to process the order application side. I’m just thinking whether charge.succeeded is as reliable as payment_intent.succeeded in deciding whether to fulfil the order application side.

fickle sinew
ionic carbon
#

Awesome. Thanks for clearing that up. I understand now. Love to see such a greatly designed API by stripe.

fickle sinew
#

My general recommendation would be to use payment_intent.succeeded and that's echoed throughout our documentation

ionic carbon
#

Thanks for your help, appreciate it!

fickle sinew
#

charge.succeeded is likely more useful for legacy implementation who aren't yet using Payment Intents

ionic carbon
#

I see, well I think that’s why I’m using charge.succeeded. The webhook has been the same from before, just the payment intent support was added into the apps

fickle sinew
#

Let me know if I can help with anything else 🙂