nkusibojoski-charge-events

[sacred acorn]

Hey! Are you using auth and capture?

[last carbon]

I'm not using auth. When I create Payment Intent I set capture_method: 'manual', to be able to do additional checks

[sacred acorn]

Yep, by passing that parameter you're essentially creating an authorisation/hold on the card: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method

Was just checking you were using that flow as otherwise charge.captured is not relevant

charge.succeeded will fire when the Charge/PI is created. charge.captured will fire when you make the API request to capture the opayment

[last carbon]

Will charge.succeeded guarantee that there is enough funds in the card so I can call paymentIntents.capture ?

Where is the right place to call paymentIntents.capture 🙂 ?

[sacred acorn]

It depends on your integration. Are you passing a payment_method during PI creation? Can you share an example Payment Intent?

[sacred acorn]

In your backend/server

[last carbon]

Sure, this is the way I create PI

[sacred acorn]

Yep, so at that point charge.succeeded won't fire (as you're not passing confirm: true)

[last carbon]

Hmmm.. strange, I can see that event in logs.
Can you please explain me what is confirm: true?

[sacred acorn]

https://stripe.com/docs/api/payment_intents/create#create_payment_intent-confirm

[last carbon]

Thank you 🙏

[sacred acorn]

So generally:

• charge.succeeded happens when the PI is confirmed.
  *charge.captured happens after, when the PI is captured.

[last carbon]

great, thank you 😊

[sacred acorn]

Np!