#Kirk-metadata
1 messages · Page 1 of 1 (latest)
Hi 👋 the key thing to understand about our metadata field is that the information provided there is not automatically transferred to other objects. So in your case, if you are providing metadata when creating a Checkout Session, then the Checkout Session object is where that information will be available, it will not be pushed to the associated Payment Intent.
Ah, that makes sense. I was under the assumption that each object that is relevant to the cascade of events would also capture the metadata from parent event to child event, but seems to be a false assumption
With the workflow I have described above (create checkout session, navigate to URL on the session, complete payment, wait for async webhook on payment_intent.succeeded), is there any way for me to grab my relevant metadata ? I didn't see a way to process a PaymentIntent object and connect it to whatever CheckoutSession it was generated from