#Richard Wilbur - checkout events
1 messages · Page 1 of 1 (latest)
Hi 👋
What events are you currently receiving? What Session ID are you referring to?
And you will likely need to make API calls to ensure you get all the correctly related info
Referring to the checkout session id, as a person could have multiple active
Okay so checkout.session.completed is a good event to start with
From the events shown on the dashboard, I may have received up to 13 events prior to that, which I'd like to link and capture
Okay, you can configure your webhook endpoint to listen to all of them
Richard Wilbur - checkout events
I see: customer.updated, payment_intent.created, customer.updated, invoice.created, invoice.finalized, customer.subscription.created, charge.succeeded, payment_intent.succeeded, payment_method.attached, invoice.updated, customer.subscription.updated, invoice.paid, invoice.payment_succeeded, and finally checkout.session.completed
Okay, you can listen to all of those if you want to.
I receive them, but I'm not sure how to link them when I have multiple members subscribing at the same time, and I may receive the events out of order, or by different lambdas on AWS
From the docs, it doesn't look like I can specify any payment intent data when creating a checkout session for a subscription
You would need to link them using the relations to each other. For instance, the Payment Intent has an invoice property that links it to an Invoice objet: https://stripe.com/docs/api/payment_intents/object#payment_intent_object-invoice which is, in turn, linked to a Subscription.
So that requires me to make API calls to Stripe rather than being able to specify payment intent metadata that I could possibly use?
We currently do. not have a mechanism to propagate metadata from a Checkout Session for subscriptions down to the Payment Intent. If you received all the events and stored the Payment Intent, Invoice, etc. you could link them yourself in your local DB.