jmak | Stripe Developers | Page 1

languid orioleBOT Feb 10, 2023, 7:16 AM

#

fossil sentinel Feb 10, 2023, 7:20 AM

#

For any changes on the connected account, account.updated event will be sent.

You may look for charges_enabled field to determine the account can create live charges and payouts_enabled field to check whether Stripe can send payouts to this account.

charges_enabled: https://stripe.com/docs/api/accounts/object#account_object-charges_enabled
payout_enabled: https://stripe.com/docs/api/accounts/object#account_object-payouts_enabled

If there's any incomplete requirements, it will be shown under requirements field: https://stripe.com/docs/api/accounts/object#account_object-requirements

candid pier Feb 10, 2023, 7:24 AM

#

is there a way that the stripe connect user will be able to fill out those fields after they leave the onboarding flow?

fossil sentinel Feb 10, 2023, 7:25 AM

#

What type of connected account are you using? Standard, Express or Custom?

candid pier Feb 10, 2023, 7:25 AM

#

express

fossil sentinel Feb 10, 2023, 7:27 AM

#

If the connect user hasn't completed the onboarding, platform can generate new account link again: https://stripe.com/docs/connect/express-accounts#handle-users-not-completed-onboarding

candid pier Feb 10, 2023, 7:28 AM

#

okay thanks, adding this endpoint now.
btw i selected connected accounts here

#

so in this case do i also select account.external_account.updated? or no

fossil sentinel Feb 10, 2023, 7:31 AM

#

External account is meant for payout purpose. For checking connect account status, account.external_account.updated is not required

candid pier Feb 10, 2023, 7:33 AM

#

okay dope. one other question. are there fields i need to expand after grabbing the account?

#

this is how i'm grabbing the account, let me know if this is wrong

#

fossil sentinel Feb 10, 2023, 7:35 AM

#

This looks right to me

#

The fields I mentioned above are included in account.updated event by default. No additional account retrieval with expansion is required

candid pier Feb 10, 2023, 7:39 AM

#

ok so for example this would be a fine check everytime the events come in right

#

for the else statement theres no additional need to prompt them to fill out info again I assume, or is it good practice to just redirect them again to the onboarding URL?

fossil sentinel Feb 10, 2023, 7:42 AM

#

In the else, you should check if there's any requirements on the account awaiting to complete: https://stripe.com/docs/connect/account-capabilities#creating

If yes, then you can redirect the connect user to complete onboarding using new account link

candid pier Feb 10, 2023, 7:45 AM

#

got it so send them to my previous endpoint for return_url

#

are the requirements that are in the account field the bare minimum to make charges_enabled and payouts_enabled?

#

basically im wondering if i should have like

verify}
if requirements {
fill out requirements
} 
// you only end up in this place for an odd reason
return unknown error ```

#

or its just fine for one if-else like

verify}
else {
// requirements are non-empty
fill stuff out in a redirect link
}

fossil sentinel Feb 10, 2023, 7:57 AM

#

Yes, requirements are the minimum for charges_enabled and payout_enabled

#

I'd recommend checking requirements field as platform can pause payout in dashboard and might not have anything to do with requirements

candid pier Feb 10, 2023, 8:00 AM

#

okay that makes sense

#

in the handle users that have not completed onboarding

#

how do i retrieve where they lef toff?

fossil sentinel Feb 10, 2023, 8:05 AM

#

Account link will pick up where the user left off

candid pier Feb 10, 2023, 8:06 AM

#

like I do a new link again?

#

result, err := accountlink.New(linkParams)

fossil sentinel Feb 10, 2023, 8:08 AM

#

Yup! Just the account link generation here: https://stripe.com/docs/connect/express-accounts#create-link

#jmak