#RobertGoddard

1 messages · Page 1 of 1 (latest)

floral stratusBOT
inland lintel
#

Hey there

north flicker
#

hello.

inland lintel
#

Can you provide a specific example that I can look at?

north flicker
#

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

inland lintel
#

Can you provide that account ID?

north flicker
#

which account ?

#

the connected account or the main account ?

inland lintel
#

The Connected Account

north flicker
#

acct_1LpxXHQVoGJHqUcj

inland lintel
#

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

north flicker
#

ohhhh

#

Thank you so much!

inland lintel
#

That will listen for events on the Connected Accounts

north flicker
#

I wondered what that meant

inland lintel
north flicker
#

Perfect, thanks

inland lintel
#

Sure thing

north flicker
#

I set up a second webhook address for Connect but it didn't work and it indicates a 100% error rate

uneven pivot
#

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?

north flicker
#

Sorry bad request, this may be on our end

#

Bad request would mean our webhook endpoint isn't accepting connections, correct?

uneven pivot
#

Probably. If you give me an Event ID I can take a look and tell you for sure.

north flicker
#

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.

uneven pivot
#

Ah, yep, that'll do it!

north flicker
#

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

uneven pivot
#

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.