#jcalentine
cinder doveBOT
Hello jcalentine, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• jcalentine, 0 days ago, 12 messages
shrewd moss
Hello again! It really depends on your integration - just for standalone payments you'd want payment_intent.succeeded
shrewd moss
Ah yeah if you're using checkou then you'll want checkout.session.completed
random knoll
so when you use the redirect to pay on stripes form, I have to use checkout.session.complete not payment_intent.succeeded
shrewd moss
It depends on what you want - if you want to know when the Checkout Session is complete then you definitely want checkout.session.completed (which will also work for async payment methods that are soetimes completed asynchronously later). payment_intent.succeeded is if you want to be sure of when payment is successful
shrewd moss
It does, but that's why I mentioned it depends on what you want - if you just want to know when the checkout session is completed you'd use that event, but if you want to know for sure when payment is complete then you may want to use payment_intent.succeeded
random knoll
basically what i need is when a payment is completed it flags 2 columns in my database to allow a user access to certain features on the web application
shrewd moss
Then you'll want to listen for payment_intent.succeeded