#tas-checkout-product

1 messages · Page 1 of 1 (latest)

visual spadeBOT
#

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.

  • tas0458, 15 minutes ago, 5 messages
  • tas0458, 8 hours ago, 7 messages
livid dune
#

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

visual spadeBOT
#

tas-checkout-product

iron mango
#

checkout.session.completed also means the payment completed successfully?

livid dune
#

Yes, that's correct

iron mango
#

I just checked the response body and this info seem to be missing too.

#

for the checkout.session.completed event

#

am I missing something?

livid dune
#

Can you share the event ID?

livid dune
#

@iron mango let me know if you still need help!

iron mango
#

evt_1OgxXNHwRDPN0Md4nNmo78Mt

#

sry.. little busy here

livid dune
#

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

iron mango
#

can I do it via golang sdk? the session id is the event id?

livid dune
#

the session id is the event id
No, the Session ID is what starts with cs_test_ (or cs_live_ in live mode). You should see it in the payload of the checkout.session.completed event

iron mango
#

ohh TY! thats a little confusing
I'll try it tomorrow and will let you know
sounds good?