#danmatthews_webhooks
tawdry kettleBOT
đ 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/1309544316485505106
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
coarse heron
Ah ok! Dangit.
Is there any way to reintroduce that balance transaction id into the webhook?
or is it missing because handling between versions changed completely.
i'm just trying to find the version upgrade we did
13.8.0 -> 16.3.0
spiral tangle
sudden sundial
@spiral tangle You need to fill out the form in #help
@coarse heron I'm looking
coarse heron
Thank you.
sudden sundial
Ok this is because of: https://docs.stripe.com/payments/payment-intents/asynchronous-capture
This is the new default behavior in latest api versions
So basically charge.succeeded won't have the balance transaction
A charge.updated event will be fired off after with the balance transaction once the payment is captured async
Which would be this event in the above example: https://dashboard.stripe.com/events/evt_3QNtZHERbNiuR56N19eV53Ua
coarse heron
Ah amazing thankyou.
sudden sundial
No problem
coarse heron
It does say it's opt-in, i assume the SDK is doing the opting in for us?
sudden sundial
The latest api version uses it by default
Our php sdk pins to the latest api version at time of release
So when you upgrade sdk, it upgraded to the api version where this was default behavior
That's why sdk upgrades should be thoroughly tested in test mode before you roll them out