ignasidedieu_api

[odd rapids]

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

📝 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.

• ignasidedieu_expanding-responses, 4 days ago, 37 messages
• ignasidedieu_api, 5 days ago, 17 messages
• ignasidedieu_docs, 6 days ago, 4 messages

[hot spire]

Hi, let me help you with this.

checkout.session.completed doesn't guarantee that the Balance Transaction is created, so I would suggest listening to charge.updated: https://dashboard.stripe.com/test/events/evt_3QrGbQLOFmVUUygj1qgSsS4l

You can see previous_attributes[balance_transaction]=null meaning the Balance Transaction reference was added during this event.

[fervent coral]

Is this something new in Stripe 28.1.0 version? Because we've upgraded from 21.3.0 and this version the current implementations works fine. The main difference is that we retrieve the charge object directly from the PaymentIntent without the need of expanding it

[hot spire]

What library are you using exactly? 28.1.0 is a library versioning, not API.

[hot spire]

Possibly, there were changes related to this recently.

[fervent coral]

We are experiencing this issue when using 28.1.0 library version. How is it possible?

If checkout.session.completed does not guarantee a Balance Transaction created, it should work exactly the same in 21.3.0, shouldn't it?

[spice nacelle]

hi! I'm taking over this thread.

yes, this changed in a recent API version: https://docs.stripe.com/upgrades#2024-04-10

PaymentIntents now has automatic_async as the default capture method when capture method is not specified during PaymentIntents creation.

so when you create the Checkout Session, make sure to set this parameter to automatic to make sure you always get a BalanceTransaction: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-capture_method