#RobertGoddard
1 messages · Page 1 of 1 (latest)
Hey there
hello.
Can you provide a specific example that I can look at?
We are onboarding an account (creating a connected account) via the stripe node api. (completing the redirect session), stripe is creating the connected account, but the account.updated event is not being sent to us
Can you provide that account ID?
The Connected Account
acct_1LpxXHQVoGJHqUcj
Ah okay
So your platform has a Direct Webhook endpoint set up. This only listens for events on your Platform Account
You need to also set up a Connect Endpoint
That will listen for events on the Connected Accounts
I wondered what that meant
Perfect, thanks
Sure thing
I set up a second webhook address for Connect but it didn't work and it indicates a 100% error rate
Hello! I'm taking over and catching up...
What errors are being reported?
Can you give me one of the Event IDs which is showing a delivery error?
Sorry bad request, this may be on our end
Bad request would mean our webhook endpoint isn't accepting connections, correct?
Probably. If you give me an Event ID I can take a look and tell you for sure.
This is on our end
I have told both webhook endpoints, the main account one, and the connect account one to go to the same backend webhook handler... They have two different signing secrets, so I'm working through fixing that on our end.
Ah, yep, that'll do it!
Would be reallllly nice if we could just have both the main account and connected account webhook events to go to the same backend endpoint using the same signing secret
You can add something like ?connect at the end of the URL and then add signing secret logic to use the right one based on the presence or absence of that query parameter.