#Richard Wilbur - checkout events

1 messages · Page 1 of 1 (latest)

open dawnBOT
hidden quest
#

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

abstract bear
#

Referring to the checkout session id, as a person could have multiple active

hidden quest
#

Okay so checkout.session.completed is a good event to start with

abstract bear
#

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

hidden quest
#

Okay, you can configure your webhook endpoint to listen to all of them

#

Richard Wilbur - checkout events

abstract bear
#

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

hidden quest
#

Okay, you can listen to all of those if you want to.

abstract bear
#

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

hidden quest
abstract bear
#

So that requires me to make API calls to Stripe rather than being able to specify payment intent metadata that I could possibly use?

hidden quest
#

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.