#brokenlaptopdev_webhooks
buoyant talonBOT
đ 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/1414650268485685268
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
calm lion
Cool, thanks
I only included a single pair of events, I have 2 other pairs of events of the same behavior
So I can send the other 4 if it's helpful
solid panther
Those are fine to start
solid panther
Okay so it looks like overall what is happening here is that the company.tax_id is briefly going into the pending_verification state when onboarding is completed. During that period of pending_verification which can either be <1 second or take up to several minutes or longer (as this is dependent on our verification with third parties) the account has payouts_disabled. Then once the verification completes Payouts are enabled.
Overall there is no guarantee on the order of Events here, see: https://docs.stripe.com/webhooks#event-ordering so in cases like this you want to retrieve the relevant object to verify its state if you seem to receive Events out of order (or you can just do this in general when receiving related Events in short-succession).
calm lion
Cool, so directly retrieving the account through the api should maintain that payouts_enabled: true even when receiving the second event with payouts_enabled: false?
solid panther
Yep
calm lion
Cool, I'll give that a try. Thank you for the assistance!