#raimund_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/1384613545169260606
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
The webhook events are delivered asynchronously and we don't really guarantee it's order.
Can you share more about the issue you're seeing??
First, we're receiving a webhook with eventType payout.paid and status failed in the object which is already a bit strange. And the webhook with event type payout.failed arrives within a millisecond. We keep track of the amount, but our status logic isn't necessarily updated correctly.
Interesting.. I wouldn't expect payout.paid event if the payout failed but maybe I'm missing something.. Let me look at the examples
Ah behavior is expected I think because failure happens after funds leave Stripe. Like we've theoretically "paid" out the funds but the bank rejected it.
OK, but is the timeframe realistic?
It is not*
*Since the webhook event delivery happens async, it is possible that the initial event may not arrive immediately when Stripe pays out funds.
The safe path here would be to retrieve the Payout object and check the status
whenever you receive the event
I see.
So the failed event can actually arrive before or virtually at the same time as the paid event?
Correct
Is it likely?
Not really, but would recommend guarding against it nonetheless
OK, thanks.