#NS-IT-payments

1 messages · Page 1 of 1 (latest)

midnight heath
#

hi there! Stripe doesn't have any way to know what websites your payments are related to really.

#

if you have multiple endpoints on your Stripe account listening to a specific type of webhook event(like a payment_intent.succeeded successful payment), we send the event to all of them, it's just how it works, it's account-level

silver wolf
#

Ah ok that makes sense - assumed the endpoint would be the diffeentiator for that

#

So essentially managing these through one account is just liable to cause some errors? Its incredibly infrequent - where it flags errors just says 'stripe blocked' - but 99%+ of everything else still goes through

midnight heath
#

you're not really supposed to use the same Stripe account for multiple businesses to be clear (https://stripe.com/docs/multiple-accounts You must use separate Stripe accounts for projects, websites, or businesses that operate independently from one another. )

as for the 402, that would be coming from your server so you'd need to check why you returned that, but overall some delivery failures are completely normal, we retry events that don't get delivered so unless you're down for an extended period of time you wouldn't miss them overall. https://stripe.com/docs/webhooks/best-practices#events-and-retries

silver wolf
#

Its managing some white label sites for clients that we create and host so within the same business - but did not consider that different websites would be the problem

#

So in this case we would need a seperate stripe account for each individual White Label site?

midnight heath
#

hard to say, one way is they would have their own Stripe accounts and you just provide the code and they configure it with their API keys and set up the endpoints (a plugin basically)
or you could use Connect where you have a main platform account that can directly call the API behalf of other Stripe accounts and receives events from all of them(https://stripe.com/docs/connect/ // https://stripe.com/docs/connect/webhooks )