piercy_api

[grand topaz]

👋 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/1298966405277814844

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

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.

• piercy_api, 1 day ago, 4 messages

[burnt gorge]

Which APIs are you using that support line items? Checkout?

[fading sand]

Yeah it would be the checkout, is there a way to get the checkout id from the payment intent?

Now i've typed that, i am wondering it would be better to receive the checkout events and then just do what i need from that.. but I didnt think the checkout events confirmed successful payment

[burnt gorge]

Yep, you should just listen for checkout.session.completed event and fetch the line items that way: https://docs.stripe.com/checkout/fulfillment

[burnt gorge]

There is: https://docs.stripe.com/api/checkout/sessions/list#list_checkout_sessions-payment_intent

[fading sand]

Ok, so just so I have this correct. If I use the checkout events

checkout.session.completed and checkout.session.async_payment_succeeded will be triggered when they get marked as paid? either immediately, or if delayed then it would be the async one that comes in later.

I just don't want to end up in a scenario, where the checkout completes, then event is fired but payment is still processing, so we don't send a receipt and then end up missing the event entirely.. but it seems the async event is probably designed to cater for that

[burnt gorge]

Yes, exactly. As noted here you'd check the payment_status on the event to understand whether you should wait for an .async_payment_succeeded event before 'fulfilling'

Only relevant if you're doing non-card payments like SEPA/ACH

[fading sand]

Perfect, thank you.