#dan-checkout-webhook
1 messages · Page 1 of 1 (latest)
dan-checkout-webhook
@regal frost you should be listening to checkout.session.completed for fulfillment when using Checkout: https://stripe.com/docs/payments/checkout/fulfill-orders
There's no way for you to control the metadata that will be put on the PaymentIntent associated to an Invoice associated to a Subscription
is checkout.session.completed equivalent to payment_intent.succeeded in my usecase of working only with subscriptions?
Hi there 👋 taking over, as my colleague needs to step away
For Subscriptions, you would want to use invoice.paid for fulfillment, since obviously checkout.session.completed will only fire for Checkout (e.g. the first time someone uses Checkout to create a Subscription payment)
I mean no. You should still use checkout.session.completed for the first part
Oh I see, so then invoice.paid would cover the first time and all subsequent times as well, correct?
yes, but I would personally still do fulfillment on checkout.session.completed for the first Invoice/Subscription creation
oh ok what's the reason for that?
because you send them to Checkout, you should be looking at their Session completion, the created Subscription, etc. Getting invoice.paid and having no record of that Subscription or where it came from will make your code go "huh wtf"