#rahuls1098_api
plucky solarBOT
đ 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/1232116250814189708
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
neat ravenBOT
hidden flicker
Hi, I just tested this on my end and I can still see the balance transaction id when I get payment_intent.succeeded event. Can you share a bit more details? Can you share the event id where this happened, it starts with evt_? Does this happen on all payments or subset of payments?
novel shale
Yes of course, will share now
And it happens on all payments
evt_3P8UaVIHF0rZ67ZR1sj4e7Zg
The balance transaction attribute is now null in charges -> data -> balance_transaction within this event
This is just one of all events that are now showing null for balance transaction. I think it's been happening for the past 12 days
neat ravenBOT
hidden flicker
Taking a look..
Can you share the event where you're seeing the balance transaction? I see that it's a connect payment. I'll test this while you get that id
novel shale
So I just click on the charge id in 'latest charge' in the payment intent succeeded event on the stripe dashboard, and it takes me to the charge.updated event which has balance transaction id
Here is that charge.updated event: evt_3P8UaVIHF0rZ67ZR15ZaXNRQ
Yes these are all from Connect accounts
Payment Intent Succeeded event: evt_3P8UaVIHF0rZ67ZR1sj4e7Zg
Charge Updated event: evt_3P8UaVIHF0rZ67ZR15ZaXNRQ
Also, separate but I was wondering if something has changed, would you be able to point me to the Stripe doc/release note documenting this change to balance transaction in the stripe payment intent succeeded event? Thank you
hidden flicker
Still looking at this on my end. Did you make any changes on your end?
After looking at this, it looks like you've potentially made a change on your end. You're using the capture_method: "automatic_async", https://docs.stripe.com/api/payment_intents/create#create_payment_intent-capture_method so the balance transaction is not created right away. That will be included on the subsequent event.
It looks like you're passing the latest version of the API, https://dashboard.stripe.com/logs/req_SMIKwvS70jAMOr and we document that this capture method is the default: https://docs.stripe.com/upgrades#2024-04-10
novel shale
Hm, I don't think we changed anything regarding Stripe capture_method, but is there somewhere in the Dashboard this can be configured?
Okay so since 4/10/24, automatic_async became the default? Maybe the change on our end was switching over to the latest API?
And if that is the case, can we stop from automatically upgrading API version (so our logic doesn't break). Thanks so much for checking this by the way
rugged copper
In stripe-php 9.2.0 (likely your system updated your stripe-php library recently), the Stripe API version has been updated to 2024-04-10, which default capture_method to automatic_async: https://docs.stripe.com/upgrades#2024-04-10
If you would like to remain the old behavior, capture_method can be set to automatic
shy trench
@rugged copper may we double check what is the default of the caputure_method before 04/10?
plucky solarBOT
@shy trench looks like you're in the wrong place, this thread is for someone else's question.
- If you have your own thread please chat there.
- If you have a question or a followup to a closed thread use one of the buttons in https://discord.com/channels/841573134531821608/842637025524842496 to get help (we don't reopen closed threads).
Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.
novel shale
We don't expliciltly set the capture_method in our code. If we explictly set it to automatic, I guess that will fix this issue
rugged copper
Yes! I'd recommend giving it a try in test mode
novel shale
I created a local listener and tested it out, looks like that it fixed the issue. Thank you for the help!