bruno_api | Stripe Developers | Page 1

cloud lavaBOT Jun 16, 2025, 1:40 PM

#

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

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

#

sharp tartan Jun 16, 2025, 1:41 PM

#

Hi, yes - you should be able to use the URL.

formal cargo Jun 16, 2025, 1:43 PM

#

Hey! Unfortunately I cannot use the UI in these tests, because we're testing it via API.

When we work with payment intents, we can use stripe.paymentIntents.confirm('pi_ID', {payment_method: 'id'})) to simulate a payment. can we do something similar with checkout sessions?

sharp tartan Jun 16, 2025, 1:51 PM

#

No, that is not supported with CheckoutSessions.

formal cargo Jun 16, 2025, 1:55 PM

#

I see.

I noticed the API returns null in the payment_intent attribute when we retrieve checkout session information, even though one (pi_3RadPcGdzAdWKmV31QVjFRFs) was generated...

#

Is that expected?

sharp tartan Jun 16, 2025, 2:00 PM

#

If you retrieve it after the creation that is expected, https://dashboard.stripe.com/test/logs/req_Kdmp1rqk1Wl3tI

If you retrieve if after the ocnfirmation: https://dashboard.stripe.com/test/logs/req_dZLhRdmoGTF3NQ it should be populated under payment_intent.id

formal cargo Jun 16, 2025, 2:04 PM

#

I see. Thank you, I will see how to proceed here

#bruno_api