#N3XUS-webhooks

1 messages · Page 1 of 1 (latest)

fading kiln
candid marsh
#

Hi,
this is not an option there are like 800 webhooks I would have to set up. We have to do this automatically.

fading kiln
#

@candid marsh you setup a webhook on the platform to listen for events on all the connected accounts

#

you don't setup one webhook url for each connected account

candid marsh
#

But the information events that are send from stripe like charge.successful e.t.c. have to be send to a specific URL of the stripe_account where this charge was made.
As I said in the beginning. There are many instances of one and the same application that are on diffrent servers with different events. There is not one single server responsible for all stripe events but each server is responsible for one account.

fading kiln
#

what connected account type are you using?

#

Express/Custom/Standard?

candid marsh
#

Thats a good question where can I find this in the dashboard?

fading kiln
#

if you go to the connect page

#

you can see the type of your connected accounts there

candid marsh
#

Ah tthanks : Standard

fading kiln
#

your connected account users have access to their own Dashboard, and they need to setup the webhook by themselves in https://dashboard.stripe.com/webhooks, it isn't something which you can set via the API for them

candid marsh
fading kiln
#

you can't do that for your connected accounts

candid marsh
#

I see ok thank you

candid marsh
#

@fading kiln Just one last question. If each client sets up its own webhook. Will I be able to "read and verify" the webhook-events if I only have the connect-stripe-secret or would I need the clients stripe secret?

fading kiln
#

@candid marsh could you elaborate a bit more on what you'd be doing with the events? Maybe we would be able to better advise after knowing more

#

i think if you're trying to create a plugin/module, you're going to need to request the user to input their webhook secret to your plugin/module