andrey-g_api

[copper flame]

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

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

[novel solar]

Hello,
 
v45.7.0 is using the API version 2024-06-20.

Starting from API version 2024-04-10 [0], PaymentIntents now has automatic_async as the default capture method when capture method is not specified during PaymentIntents creation.
 
If you are using automatic_async, what this means is :

For all payments, the balance_transaction is null on the following objects. For Connect payments, the transfer and application_fee are also null on the following objects:

• attached Charge object of the API response
• charge.succeeded webhook
• payment_intent.succeeded webhook

You can see find out more about why you would want to use automatic_async and how to be notified when the balance transaction is available here : https://docs.stripe.com/payments/payment-intents/asynchronous-capture
 
Alternatively, you can explicitly pass in capture_method="automatic" [1] if you wish to receive the balance_transaction immediately

[0] https://docs.stripe.com/upgrades#2024-04-10
[1] https://docs.stripe.com/api/payment_intents/create#create_payment_intent-capture_method

[tired holly]

Thanks Alex,

Seems like that's exactly what I was missing!