Erith Ikezawa - Checkout Metadata

[dark hedge]

Hello! That's expected, Checkout Sessions and Payment Intents have independent metadata that does not overlap.

If you want to see the metadata on the Checkout Session you should listen for checkout.session.completed to get an Event containing the Checkout Session.

[white plover]

I assume there isn't a way to use that paymentIntent to fetch an associated checkout session?

[dark hedge]

When creating a checkout session, is there a difference between manually bouncing users to the generated Stripe\Checkout\Session->url and using the Stripe JavaScript to redirect to that same checkout session?

There's no real difference, no. Using the URL is generally easier and recommended.

[white plover]

Sorry, thought that since it was a different subject it'd be better to go for a new thread.

Makes sense, I'm not sure why old code was using js for the redirect over the URL and I wanted to be sure that nothing would break Stripe side if I swapped over

[dark hedge]

Originally we required Stripe.js to redirect to Checkout as there was no URL property, it's likely you wrote that code when that was the case.

When the url was added to Checkout Sessions it became the recommended thing to use, but we still support using Stripe.js to redirect as well.