#theddev_webhooks
1 messages ยท Page 1 of 1 (latest)
๐ 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/1333815587901800530
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello there
Hello sir
We outline this in the API Reference: https://docs.stripe.com/api/payouts/object#payout_object-trace_id
Basically we can't guarantee that it will be provided at the time of payout.paid as we rely on communication from the bank for that.
So no, can't ensure that it will be present.
yes I understand that but I want to know if you can notify us(webhook) when you have that information from the bank?
or, the only way to get is via requesting the payout information using api regularly till we have that information?
Right now the only way is to poll the API, yes.
Err actually one sec.
Let me check if we fire payout.updated in this case.
Ah yes indeed we do
okay thank you sir.
I could only see these three events and don't see payout.updated in the events
Yeah that is in test mode and the trace_id hasn't been updated there.
It will fire in live mode.
oh okay, so this issue is limited to sandbox, provided we have implemented the payout.updated
understood, thanks sir.
no but when we retrieved the information using Api we could see the traceid
Ah yes you are right -- I can see it on the object. Okay well that looks like a test mode bug that I can report.
We should fire payout.updated there. I do see that webhook being fired in production for trace ID updates.
on left: the webhook body
on right: the api callout response
Feel free to take a look at your production instance to verify.