andy_python-upgrade

[timber kelp]

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.

• andy_unexpected, 2 days ago, 4 messages

[tacit grove]

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1256004148332331059

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

[whole sandal]

@pseudo burrow it's related to https://docs.stripe.com/upgrades#2024-04-10 with the change

PaymentIntents now has automatic_async as the default capture method when capture method is not specified during PaymentIntents creation. For more information about async capture, view the asynchronous capture guide.

The PaymentIntent is now captured asynchronously and the BalanceTransaction and ApplicationFees associated are created asynchronously so you need to listen for charge.updated where those get set now. See https://docs.stripe.com/payments/payment-intents/asynchronous-capture

[pseudo burrow]

got it, thank you!