#zaq_webhooks
1 messages ¡ Page 1 of 1 (latest)
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.
- zaq_unexpected, 15 hours ago, 13 messages
- zaq_connect-sct, 19 hours ago, 7 messages
đ 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/1235671689979756554
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
I guess I am also just wondering if there ARE transfer.success or failure messages ever? I want to make sure I'm handling this transfer process as well as I can
Hey there, you're seeing this transfer related to this destination payment: https://dashboard.stripe.com/test/logs/req_ZguLF95YRvima4
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Those are create for you and shouldn't fail
https://docs.stripe.com/connect/destination-charges?platform=web&ui=elements#flow-of-funds-app-fee
yep. i just wanted to double check. would stripe ever send my webhook a transfer.succeeded message? do those exist? or is it just the transfer.created/reversed/updated
Nope, just those three that I'm aware of, it should fail or succeed synchronously (even when you create it directly, outside of a destination payment), so an async success event is not necessary