#jaybell_apiupgrade-autoasync-capture
teal roostBOT
👋 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/1261372466878484642
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
soft current
Looks like this request: req_wTr7CWC9Y8zHEB the charge we are making with a saved payment method is correctly expanding the latest_charge property but even there the balance_transaction is null (same with source)
frozen storm
I upgraded from 2019-05-16 to 2024-06-20
That is a huge jump.
I would expect a lot of breaking changes in that case
soft current
I read through the changelogs and the majority of changes don't actually apply to us (we aren't using subscriptions or invoices and all that).
anything related to charges/transfer etc didn't seem relevant either (other than the one I mentioned). Are there other breaking changes not lsited there?
frozen storm
No, that should be all of them
soft current
Ok so maybe simplify this down then req_wTr7CWC9Y8zHEB this charge, why is there no balance_transaction, source, or transfer on it? (there used to be on the old version), it is a destination charge.
frozen storm
Taking a look at the request
soft current
thank you
I looked at the expanded changelog (https://docs.stripe.com/changelog) as well and didn't notice anything by searching., but theres a lot there.
frozen storm
Oh wait, yeah this is because we now default to confirming async, isn't it?
soft current
Oh it definitely could be.
frozen storm
I'm looking at the Charge and I see all those properties have values
soft current
ok i see that here
https://docs.stripe.com/upgrades#2024-04-10
frozen storm
Yup! That's what I thought
soft current
looking at our code
frozen storm
But I can see how it would be easy to miss
soft current
ok so changing that to automatic from the default automatic_async should do what I want I would assume?
I can give it a try right now.
frozen storm
Yup, that should restore the behaviour you were used to
soft current
Will report back in a couple min, thank you!
frozen storm
Confirmation requests will take a bit longer but you should have the properties populated with the data you want
soft current
Are they slower than they used to be (on the previous version)? Or just slower compared to the async option now?
Cause I was fine with how they were earlier tbh
frozen storm
I think it was a move to reduce latencies compared with our previous behavior. I don't think we are slower than before, no.
soft current
Yup that did it! I appreciate it thank you very much!
I will keep us up to date more often from here on out, I probably would have put the pieces together quicker if I only had to read one or two changelog entries and not lots of them.
frozen storm
No worries! I'm glad we were able to track down the issue 🙂
soft current
thanks for your help, have a great day!
frozen storm
You too.