#Imdad-inactive-account-capability
teal halo
Checking!
Looks like there is outstanding verification info for the account
You can see this on the requirements hash on the Account object: https://stripe.com/docs/api/accounts/object#account_object-requirements
teal halo
There's test data you can use to onboard accounts: https://stripe.com/docs/connect/testing
We don't need real data
edgy harbor
okay let me take a quick look
jmm
I can't see the requirements hash
when retrieving the account object via the api
can you tell me what requirements you saw that were needed
teal halo
Doesn't look like the account was onboarded at all: https://stripe.com/docs/connect/connect-onboarding
edgy harbor
waiy
which account are you referring to
our platform account?
or the other account i have been testing with
teal halo
The Custom connected account: acct_1JzIHw2U5qCS3ZcA
edgy harbor
I'm confused as to why this is necessary. We've never done this before for our Connect accounts, let alone on our testing environment.
teal halo
All connected accounts need to be onboarded, even in test mode (although we provide stubbed data - that I shared - that you can use to trigger specific account states as required)
edgy harbor
Is this for the legacy payments capability only?
As again, we've never needed to do this before to create payment intents for example where the destination has been a connect account
Actually, when I view the account on the Dashboard
It has been onboarded...
teal halo
Let me check
Yeah, so there's outstanding requirements for that account in order to enable that capability. You'll need to create an Account Link (with type: 'account_update) to bring the user back online to provide the required info: https://stripe.com/docs/api/account_links/create
You can see this on this capability.updated event that fired following the Account update: https://dashboard.stripe.com/test/events/evt_1JzK5q2U5qCS3ZcABE22seNe
teal halo
Np!