#befa_webhooks

1 messages · Page 1 of 1 (latest)

sudden gobletBOT
#

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

📝 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.

glass torrent
#

👋 Hi there! Let me take a look

chilly yew
#

Hello Arran. Thank you for your help

glass torrent
#

Do you have an event ID that's not being delivered?

chilly yew
#

Sure, this is the ID of a connected account creation req_f3Lnu3uhVGCsSc which didn't triggered any event sent

glass torrent
#

That's a GET request to retrieve an account; it would not create an event

chilly yew
#

Soory wrong line : here it is req_9ZW1qXkwBpoZvP

glass torrent
#

OK, so you'd be expecting an account.updated event I guess?

chilly yew
#

Indeed

glass torrent
chilly yew
#

But there are some, and I received webhooks until yesterday 12:03

glass torrent
#

Can you share an event ID (evt_…) that you did receive?

chilly yew
#

Here is a screenshit of my account with webhooks that seems active

Capture_decran_2026-02-25_a_11.01.59.png
#

Here it is : evt_1T4JORGLAE82xUHRr2uLFffZ

#

Or another one related t a PaymentIntent succeeded : evt_3T4IivGLAE82xUHR1tBKcPKR

glass torrent
#

Those two are related to your platform, rather than a connected account

chilly yew
#

Sorry I don't get it

sudden gobletBOT
glass torrent
#

Can you open the the first webhook in your screenshot, and share the ID (we_…)?

chilly yew
#

I think the v2 isn't used. But here is the id of the webhook named Account update endpoint : we_1T2YO8GLAE82xUHR7mvMD7Mz

#

Here is the ID og the first webhook (V2) : ed_61UBwP9OPuV2U6VrD16SmYW58cDPypHaW8mxYoShUUOm

crystal sparrow
#

For the request in question (req_9ZW1qXkwBpoZvP), this triggered an account.updated event (evt_1T4epk7tck4fMtlVMmZwqi6B), for which you need a Connect webhook configured. As arran mentioned, the other event IDs you listed happen directly on the plaform account, so these were successfully sent to the Account webhooks that you have set up. You can see more details about the different types of webhook here: https://docs.stripe.com/connect/webhooks

chilly yew
#

OK, but what about this webhook : ed_61UBwP9OPuV2U6VrD16SmYW58cDPypHaW8mxYoShUUOm Isn't it supposed to receive events for connected accounts ?

#

And on the sandbox connected accounts events where sent to this webhook we_1SryXeQG6G0kBU39GyZaJNQm which seems pretty similar to the one I created in production. Did I miss something ?

crystal sparrow
#

Looks like webhook is currently just listening for v2.core.account.updated events. I think you'll need to also add account.updated

#

The sandbox webhook does listen for this event, which would explain the difference

chilly yew
crystal sparrow
#

Ah, yes, probably. You will need to create a new webhook endpoint, and it should let you select the event from the creation screen

chilly yew
#

OK, let me try. Thank you