#dishant_bankdebit-balancetransaction
cunning bluffBOT
đ 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/1243218523879112704
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
dense cloak
spark rampart
what is the order of these 2 events
right now as I m seeing in my dashboard always succeed called before updated
Is it the flow?
dense cloak
Hm wait I think I misread your question
Balance transaction should still be in charge.succeeded
Can you share an example event id?
spark rampart
"evt_3PJcZ4JND8ucx30g0foFhgqu"
after this event immediate charge.updated occurred and that contains the balance transaction id not in charge.succeeded
dense cloak
Ah ok I know what's happening
You created the Payment Intent with the new 2024-04-10 api version: https://dashboard.stripe.com/test/logs/req_7gXvVzSus1RKCq. In that API version we made asynchronous capture the default capture_method on PaymentIntent. This leads to a successful Charge creation with balance_transaction: null in charge.succeeded for example or during confirmation and requires waiting for the capture to happen. https://docs.stripe.com/upgrades#2024-04-10
spark rampart
so whatever I am doing right now is that okay or I need to change the API version
because this is the production I can not make much changes
dense cloak
What you're doing now is fine
You have to be careful with sdk upgrades though
You're on 44.3.0 which is pinned to that api version
So you inadvertently changed prod by upgrading to that sdk version because it also changed your api version
spark rampart
ohhkk
then for now I am going ahead with current flow
thanks for the clarification
dense cloak
No problem
spark rampart
I am storing this chat link for future use
can this link be available in future as well?
dense cloak
Yep it'll be available. The thread will eventually be locked, but you will still be able to read it
spark rampart
great, thank you
cunning bluffBOT