#davidski42
ruby pike
soft lintel
Thanks. 🙂
pearl shoal
Hmm okay bit of a strange flow but overall it uses Card Element to create a PaymentMethod. In these "custom flows" where you use PaymentIntents you basically just need to care about the payment_intent.succeeded and payment_intent.payment_failed Events (also referenced here: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#web-post-payment though this is a different flow as the one you are using is a bit more legacy).
You are also using manual capture in this flow, so you may also want to listen for payment_intent.amount_capturable_updated like is discussed here: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method#capture-funds
Mostly, for fulfillment, you just care about payment_intent.succeeded
soft lintel
Cool. Kinda gross from the 3rd party developer side, but I appreciate the help!
One follow up, if I was to contact the 3rd party developer to ask about an update, is a "checkout flow" the right terminology I should be using to mirror what is generated by PaymentLinks?
pearl shoal
Stripe Checkout is our hosted flow yes.
Payment Links create Checkout Sessions
But you can also create them directly which gives you more control and a more 1-to-1 experience
(As opposed to Payment Links which is designed for 1-to-many)
soft lintel
Right. So the developer should be creating checkout sessions instead of card elements/paymentintents only, right?
For some value of "should" 🙂
pearl shoal
Well the two flows are completely different really
So it mostly depends on the goals
Neither is "right or wrong", they are just different.
Currently the third-party flow you are using is using a legacy server-side confirmation flow
We do offer a newer and cleaner flow for that which uses Payment Element
But we still support these legacy flows for older integrations
soft lintel
Gotchya. That's helpful as well. Thanks once again!