stefandespot_webhooks

[obsidian flume]

👋 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/1488477846950248560

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• stefandespot_api, 23 hours ago, 13 messages

[proven prawn]

👋 Yes, this can be expected in test mode, as there's obviously no real bank network transfers, so payouts transition through their lifecycle (pending → in_transit → paid) almost instantaneously. This means that by the time your payout.created webhook is delivered, the payout may have already reached status: paid internally, even though the Dashboard UI may briefly still show "In transit to bank" due to a slightly different refresh cadence. The same wouldn't be true for production. You'll see the expected progression of distinct statuses over time, each with its own corresponding webhook event