#tas-checkout-product
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
The PaymentIntent in this case won't have product details; it will only reflect the amount of the charge
You likely want to listen for checkout.session.completed events and inspect the line items
tas-checkout-product
checkout.session.completed also means the payment completed successfully?
Yes, that's correct
I just checked the response body and this info seem to be missing too.
for the checkout.session.completed event
am I missing something?
Can you share the event ID?
@iron mango let me know if you still need help!
Ah, this one got me earlier this week, too. line_items on a Checkout Session is an expandable field. This means it's not included in checkout.session.completed events. Instead, you'll need to make a separate call to retrieve the Session and expand line_items, or make a call to /v1/checkout/sessions/:id/line_items
can I do it via golang sdk? the session id is the event id?
the session id is the event id
No, the Session ID is what starts withcs_test_(orcs_live_in live mode). You should see it in the payload of thecheckout.session.completedevent
can I do it via golang sdk
Yep, you can. You can see a short example here: https://stripe.com/docs/api/checkout/sessions/line_items
And here are our docs on expansion: https://stripe.com/docs/api/expanding_objects
ohh TY! thats a little confusing
I'll try it tomorrow and will let you know
sounds good?