#ade

1 messages · Page 1 of 1 (latest)

woeful yewBOT
past condor
#

No explicit limit as far as I know

marble ravine
#

thanks

#

also two more questions @past condor ,

  1. does details_submitted on an account means the account is done with the onboarding via account link?

  2. if details have been submitted via link. and for one reason or the other, stripe refuses to enable the account, what properties should I look out for in the account on account.updated webhook so I can disable the account on my side too

past condor
#
  1. does details_submitted on an account means the account is done with the onboarding via account link?
    Yes
#
  1. if details have been submitted via link. and for one reason or the other, stripe refuses to enable the account, what properties should I look out for in the account on account.updated webhook so I can disable the account on my side too
    Good question, not remembering off the top of my head but looking in to it.
dire loom
#

👋 stepping in

#

You mostly want to pay attention to the requirements property on the account object

#

That will give you the most details about what the status is of the account

#

For a quick snapshot, you can look at charges_enabled and payouts_enabled

marble ravine
#

@dire loom I cannot see any requirements property on accounts

dire loom
#

What Connected Account type are you working with?

marble ravine
#

@dire loom express account

#

I am checking in the webhook

dire loom
#

Can you share an account.updated Event ID that you are looking at?

marble ravine
#

one sec

#

evt_1Me76rFztQYTRcZLfHjJtcOd

@dire loom

dire loom
#

No need to tag me 🙂

#

Looking

#

So yeah on that Event you can see: requirements: { alternatives: [], current_deadline: null, currently_due: [], disabled_reason: null, errors: [], eventually_due: [ "individual.dob.day", "individual.dob.month", "individual.dob.year", "individual.ssn_last_4" ], past_due: [], pending_verification: [] },

marble ravine
#

cant see it

#

looks like only stripe users can see that

dire loom
#

Okay let's back up

#

That Event was not sent to your endpoint afaict

#

Looks like you created your Connect endpoint after that event was triggered

#

You absolutely should be able to see that requirements hash in your webhook handler

marble ravine
#

fair

#

I think I can also see it in the account detail when i retrieve the account like this

image.png
#

so is it safe to assume that whenever this requirements.errors is not empty then the account isnt safe use

dire loom
#

No disabled_reason is what you would want to rely on

#

errors can show up before an account is actually disabled

marble ravine
#

okay thanks