luigi_checkout-metadata | Stripe Developers | Page 1

rough sigilBOT Apr 14, 2026, 11:55 PM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1493761626460131429

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

lavish burrow Apr 14, 2026, 11:55 PM

#

luigi_checkout-metadata

#

@warped sequoia the metadata you passed in those requests is set on the Checkout Session object. The corresponding Event checkout.session.completed would have the same exact metadata

#

Can you give an example Event where the data is missing so I can have a look?

warped sequoia Apr 14, 2026, 11:58 PM

#

sure:

checkout.session.completed for a checkout created in a connected account: evt_1TMG7OFZjWjAEtFMgPhtWQJt
checkout.session.completed for a checkout created in the main account: evt_1TMGlCFZjWjAEtFMlC8cykHt

rough sigilBOT Apr 14, 2026, 11:59 PM

#

warped sequoia Apr 14, 2026, 11:59 PM

#

also, the first request id is for the checkout created in the connected account. Second one is for the main account

lavish burrow Apr 14, 2026, 11:59 PM

#

how did you get that Event exactly?

#

Basically evt_1TMG7OFZjWjAEtFMgPhtWQJt is the result of something you did manually in the Dashboard in Workbench with a blueprint. It does not have any metadata.
I think you might be mixing up the Events between what your own code does/run and what you do manually in Workbench

#

@latent hearth on my team is taking over but I wanted to clarify this first

latent hearth Apr 15, 2026, 12:00 AM

#

👋 catching up

warped sequoia Apr 15, 2026, 12:01 AM

#

lavish burrow how did you get that Event exactly?

through the webhook

#

Basically evt_1TMG7OFZjWjAEtFMgPhtWQJt is the result of something you did manually in the Dashboard in Workbench with a blueprint. It does not have any metadata.
I think you might be mixing up the Events between what your own code does/run and what you do manually in Workbench
tbh I don't even know how to do that. I got this event when I finished filling the embedded checkout in our test website

latent hearth Apr 15, 2026, 12:06 AM

#

evt_1TMG7OFZjWjAEtFMgPhtWQJt was created by https://dashboard.stripe.com/acct_1Swn3nFZjWjAEtFM/test/logs/req_O6J1QoDKdtxTW9 <- created via workbench
evt_1TMGlCFZjWjAEtFMlC8cykHt was created by https://dashboard.stripe.com/acct_1Swn3nFZjWjAEtFM/test/logs/req_VU8w8VhSRQIp2y <- a backend request passing metadata

warped sequoia Apr 15, 2026, 12:13 AM

#

yeah okay, I see the confusion now

#

someone did create this event via the workbench, and since I was testing the checkout at the same time, I got both mixed up

#

in fact, I don't even receive the events from the connected account in the main's account webhook

#

thank you both for the help, I don't think I'd be able to catch that 😄

#luigi_checkout-metadata