#Nadiya-multiple-account-webhooks
1 messages · Page 1 of 1 (latest)
actually both, testing with CLI on local
currently, i'm trying to do some testing on non local environment
And are you using Connect? Or are these just separate, unrelated Stripe connects?
not using connect
just multiple individual stripe accounts
https://discord.com/channels/841573134531821608/933391853368254564
this is the reason why i use multiple stripe account instead of stripe connect
Got it
Yep, you can login to multiple accounts the CLI and then pass the -p flag when using trigger/listen: https://stripe.com/docs/cli/flags#flags-project_name
in local its okay
i've issue in non-local environment
i'm using laravel, and its fetching the webhook secret key from the env file, and all of the stripe tutorials fetch the key from env.
Is it possible to fetch the secret key from database?
there may be multiple stripe accounts in database, and ideally we may need to listen for all of them
so, how to provide the webhook secret for validating webhook signature?
That's not really a Stripe issue, but more of a general development question specific to your integration
Generally you should be using Connect, which alleviates all these pain points
we can't use stripe-connect, since client persist to not use stripe-connect regardless of our efforts to explain them about connect
then let me rephrase my question
is it possible to listen to multiple stripe account's webhook in single project?
Yep, of course. You'd just configure multiple webhooks to point to the same endpoint/URL
How you then figure out which accounts/webhook those events came from is the tricky part
oh.. well.. that's another question i wanted to ask
Yeah, there's nothing on non-Connect webhook payloads to easily figure that out
Where as a Connect event has the account field
hmm.. i see.. i probably have to drop the idea of webhook and then manually process the data based on the payment intent returned after successful payment
What is the opposition to Connect? It will really make your life a lot easier!
- they don't want to manage users payments(they just want to provide the services, and don't want to handle user's-and their customers payment related queries)
- "if there is a very bad users who create some troubles on the platform with their customer endusers, then the credit of the platformer from Stripe company decreases and Stripe has the right to suspend the platformer's account, which in turn means the suspension of entire app system."
copy-pasted from the above thread link