#Ayush9200

1 messages · Page 1 of 1 (latest)

balmy starBOT
gray socket
#

Hello! Can you give me some more details here? which webhook endpoint ID are you expecting these events to go to, and what kind of event types are you not receiving?

#

@dense rapids justing wondering if you saw my question

dense rapids
#

I am looking for this event "account.updated" which is not triggered from stripe. Rest of the other events that have added are triggered like "payment_intent.succeeded" ,"customer.created"

#

And if you see this screenshot for the events that I have configured for webhooks, account.updated is there

gray socket
#

Do you have an example connect account ID you're expecting an account.updated event for that I can check?

dense rapids
#

sure, This is one of them - acct_1MvQCFQbFyF1hUIu

gray socket
#

Ah, I see the issue - is the webhook endpoint you created an Account webhook or a Connect one?

dense rapids
#

connect account

gray socket
dense rapids
#

It says "Account"

gray socket
#

Yeah, so that's the problem - Account webhooks only receive events that are generated by your own account (the platform). If you want to receive the account.updated webhook events that are generated by your connect accounts you need to create a Connect type webhook endpoint (see https://stripe.com/docs/connect/webhooks)

dense rapids
#

oh ok let me check that.

#

But this was not the case with my previous account, I used to get all the webhooks even from Connect account triggers with "Account" type webhooks.

gray socket
#

That shouldn't be the case - if you share your previous account I can take a look and confirm, but as far as I know a regular Account type webhook should never be getting account.updated webhook events

dense rapids
#

Is it possible for "Local Listeners" to get all web hooks?

#

How can we manage two webhooks in same project considering they both have different signing secret keys

gray socket
#

Sorry I missed that first question - by "local listener" do you just mean one that you're testing through the CLI?

dense rapids
#

Yes on my local enviroment

gray socket
#

You can use the --forward-connect-to flag with the stripe listen command to use it as a connect webhook endpoint

#

So if you wanted to listen for both you could do stripe listen --forward-to http://localhost:4242 --forward-connect-to http://localhost:4242

dense rapids
#

Thanks for the help!