#brianc-webhook-connect

1 messages · Page 1 of 1 (latest)

vast pine
#

Hello @swift fern

swift fern
#

Hello

vast pine
#

hey sorry, got distracted my bad

#

How are you using Connect? Are you doing Direct Charges on connected accounts? Do you have an example Event id evt_123 I can look at?

#

But yes I think you have misunderstood webhooks/Connect quite a lot

#

if your platform has 3 Connect webhook endpoints, then every Event on every connected accounts will be sent to those 3 endpoints

swift fern
#

I'm on a call now. Sorry. I do understand webhooks but it's crazy to have all enpoints hit doen't you agree?

vast pine
#

No I definitely don't agree

#

You can have at most 16 endpoints in your account, so you can't really have one per connected account, not if you plan to have more than 16

#

so you likely misunderstood something in your setup

#

usually you have one endpoint, it gets all events and processes them as needed

swift fern
#

right now we have a ton of errors in. - on a call give me 5 min

swift fern
#

Let's start from the other end. We have multiple businesses each with entirely different apps, databases, webhook addresses. Each business is under our master account as a Standard connect account where charges are made to the Statndard and our Master account simply receives a platform fee. How are webhook enpoints set up here so that when a purchase is made from one of the Standard connected accounts, it is directed to the correct server?

vast pine
#

That is basically impossible

#

You have one Connect webhook endpoint, it gets all Events and then you dispatch it to the right place yourself

swift fern
#

That is unfortunate. We built an entire system and scalable marketplace on a faulty idea then. I find that hard to fathom. We must have gotten some bad advice somewhere along the line. How does one scale out a marketplace with multiple buisnesses who run on multiple databases without the ability to specify? I gues create some sort of redirects but htat seems like a security issue. Weird. This is the first time we've run into a problem this big using Stripe. Thanks for the clarification but are you 100% sure it is impossible to setup the scenario described?

#

Wait. Couldn't we just set up each Statndard account to connect to our Master acocunt and reverse the process?

vast pine
#

I don't understand what that could mean

#

you already said they were associated with your master account

swift fern
#

Our master account could be connected to the Standard account. flip the relationship so our master acocunt gets a fee and we set the endpoint to be on the Statndard account. Same end result. correcxt?

#

Statndard becomes the master for each one. That would work right>

#

?

vast pine
#

no that doesn't make sense

swift fern
#

Why not?

vast pine
#

because that's not how Stripe Connect works

#

You're the platform, you have one account. All other accounts connect to you so that you have one set of API keys and can accept payments across all of those connected accounts while keeping a fee for yourself.
There's only one platform account: yours. Every other account is its own business, they have their own Stripe account, just connected to your platform

swift fern
#

right. which makes it even more crazy that we can't assign an endpoint for each business which has its own database, customers, etc. I guess we'll have to create some redirects in our app so we can update multiple databases. Not the most secure solution. Sorry to be finding this out now but our fault for not triple checking prior to launchuing. Thanks for your help

#

Just to recap. When a transaction is made on a connected account it will try every endpoint listed in the master account until it find one that works? Looking ofr a quick band-aid for now.

vast pine
#

no

#

it will hit every Connect webhook endpoint. And it expects all of them to work

swift fern
#

OK. But it will hit every endpoint until it receives a 200 response from one of them, correct? It won't retry if it gets a 200 from one of them is what I am asking.

vast pine
#

no that is totally incorrect

swift fern
#

It won't retry the successful enpoint but will eventually stop trying the others?

vast pine
#

it expects a 200 from every single endpoint

#

that's the whole point of webhooks.

swift fern
#

It's what you just said. Not talking about what it expects, talking about what happens.

vast pine
#

I did explain what happens exactly

swift fern
#

And I asked you to confirm

#

simple

vast pine
#

it will hit every Connect webhook endpoint. And it expects all of them to work

swift fern
#

Right, but if one does work, it stops hitting that one, and keeps hitting the others for 3 days. Correct?

vast pine
#

yes that's correct. And hopefully they all just work immediately, because if they don't then they can get disabled

swift fern
#

Thanks. That's all I was asking.

vast pine
#

Do you have an example Event id I can look at?

swift fern
#

no. we're done. thanks!

vast pine
#

Sure, was just trying to offer you an alternative but all good!