#nerder

1 messages · Page 1 of 1 (latest)

slender nicheBOT
void beacon
#

Hello

grand hawk
#

Hey!

void beacon
#

So Connect endpoints will receive all Events that take place on the Connected Account for the types that your endpoint is listening for.

#

Are you working with Standard Accounts such that the Connected Account user might perform some actions on their account?

grand hawk
#

yes

void beacon
#

And you don't want to handle those actions via your Webhook handler?

grand hawk
#

correct

void beacon
#

Okay in that case you should set metadata on the actions that you take on the Account

#

Then you can only perform actions via your Webhook code based on the presence of that metadata

grand hawk
#

ok, right now I was doing it like this, for instance for customer.subscription.updated:

if (subscription.application === null) return;

#

basically my understanding of this was, "if the subscription object I receive has application, it means that has been updated/created by my integration"

#

will this work for this specific case?

void beacon
#

Yep that would work for Subscriptions specifically

grand hawk
#

ok, that's enough for my use-case then

void beacon
#

Then yeah you should be good to go

grand hawk
#

but this is opening a strong case for migrating to express actually

#

since we are at it I would like to ask you a question

void beacon
#

Sure

grand hawk
#

for Connected Express, the connected account will be able to do operations in the dashboard such as creating and deleting subs?

#

like they will do with the standard?

void beacon
#

Nope

#

With Express they have a very limited Dashboard where they can basically just read info about payments/payouts and update account verification info and their external account

grand hawk
#

ok!

#

understood

#

and last question then, what about the connect custom?

#

they will have access to the dashboard as of the standard or as the express one?

void beacon
#

With Custom we don't provide a Dashboard at all

grand hawk
#

ah ok!

void beacon
#

You would build the Dashboard yourself with whatever info you wanted to provide to your users

grand hawk
#

ok this makes sense, so to recap if i've understood properly

#

standard is when basically they have the dashboard, we can do things in their behalf but they can also do stuff (so we need to account for that and be careful of only handle stuff that concerns us)

#

with express, they will have some views on payout and some readonly functionality

#

and we custom we need to implement the dashboard ourselves as a standalone product

void beacon
grand hawk
#

thank you so much @void beacon, hopefully you had a great xmas

#

happy new year!

void beacon
#

Thanks, you too!

grand hawk
#

talk soon

#

👋

void beacon
#

👋

grand hawk
#

hey @void beacon sorry to bother again, reading that doc triggered me another question

void beacon
#

Sure

grand hawk
#

but is possible for standard to handle the onboarding without using the stripe's one?

#

or that will only be available for custom?

void beacon
#

Not completely, no.

#

You can't accept ToS for a Standard Account

#

They have to go through the onboarding flow to do that

#

You can pre-fill a good amount of their info to minimize onboarding

#

But Custom is the only one that isn't required to go through the Stripe onboarding flow

grand hawk
#

ok understood

#

generally speaking on an order of magnitude, how much complexity adds to support an integration for custom vs standard?

#

we are talking a huuge chunk of work, or is mainly the business logic to manage the onboarding?

void beacon
#

Mostly just depends on what you are trying to build and what you want to provide to your users

#

The onboarding and account updates for verification information is the minimum difference, mostly.

#

But you likely will need to provide some sort of UI to your users.

grand hawk
#

ok yes I see

void beacon
#

There is also the liability shift with Standard vs. Custom that you may want to consider

#

So you'll want much better fraud prevention measures with Custom

#

Versus with Standard you can rely on Stripe to handle more of that

grand hawk
#

yes I see

#

this is the problem

#

seems like that for having the flexibility to handle the onboarding you also need to carry the weight for the added liabilty

#

eheh a little dilemma

void beacon
#

Yep pretty much!

grand hawk
#

just for giving you context tho, we are building a SaaS for gyms

#

at the moment we have everyone of Standard

#

but onboarding new customers is a big pain and also they are not really savvy enough to handle the dashboard complexity

#

thats why we are evaluating different approaches

void beacon
#

Yep that all makes sense

#

It basically all comes down to trade offs

#

And what you care about the most

#

To me, Express likely sounds like the way to go for your model

#

It is the "in between" so to say

#

But your platform will still be fully liable with Express

#

So do have to be careful there

grand hawk
#

Ok, I'll explore that more in details

#

thank you so much again

#

this conversation was pure gold!

void beacon
#

np!

grand hawk
#

can i download it to share it with my co-founder?

void beacon
#

No download feature on discord as far as I know. I think you are best off with a copy/paste

grand hawk
#

I'll go with that

void beacon
#

Or, the convo will get archived and you can come back to it later on