#trizzy-_webhooks
steel questBOT
👋 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/1486577275636809818
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
⛔️ Stripe developers have stepped away for a short while
Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.
Hello @pseudo totem, we have sent you a direct message, please check it at https://discord.com/channels/@me/1486579869906370601
- 🔗 The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
fluid juniper
Hey @pseudo totem I would need to take a look at your dashboard to check the webhook configurations, could you grant me access?
pseudo totem
For sure, done. Thanks!
fluid juniper
Do give me some time to look into this!
pseudo totem
No worries! Take your time, I appreciate the help
fluid juniper
Hey! Thanks for the wait
Could you try creating a Account Webhook with the source set to “Your account,” and then trigger those events again?
To elaborate, events like evt_test_65UOT1loT9p2B6GxtVS16UEqTr9IA8RxUfvZBfHgOO0JbU (v2.core.account[configuration.recipient].capability_status_updated) are treated as from the Account itself. This concept was introduced with V2 Accounts, but the documentation hasn’t made this very clear yet.. I can put together a more detailed explanation if needed, but it will take a bit more time.
In the meantime, I’d suggest you try setting up a new account webhook to listen for those specific V2 events, trigger/retrigger those events and check if they are now delivered as expected.