#dev-in-need_docs
drifting emberBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1267598212198432769
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
dense ingot
Hi there
Just to make sure, do you intend to allow your connected accounts to be able to pay out funds from their Issuing balance to an external account? If so, you should have the connected accounts complete the requirements for external_account
If you don't want your connected accounts to be able to pay out funds from their Issuing balance then you can ignore the requirements for external_account
manic cradle
I do want them to be able to withdraw from their issuing balance to their external account they linked during onboarding
dense ingot
Got it. In that case, you can ignore any requirements related to external account
manic cradle
oh but sorry arent you saying I do need the requirements for external_account?
since they are going to withdraw to the default external account?
the withdraw is a payout essentially
for example one of the connected accounts I created in production today says
This account may have more requirements due in the future.
If it processes enough volume, more information will be required to avoid an interruption in service.
Which is regarding the owners social and document verification.
So in terms of this requirement would it be coming in the eventually_due for the issuing or is this a requirement for something other than issuing and external_accounts
dense ingot
the external account requirement you can ignore is the one related to the card_issuing capability
manic cradle
ok so they wont run into issues payout their issuing balance to their external account they added through onboarding?
because when I create the session I add in the components[account_onboarding][features][external_account_collection] and set it to true - because the default is what I use for the payout
dense ingot
Oof, I'm sorry. I totally read this as "you don't want to allow them to withdraw..."
Do you have a connected account ID I can review?
drifting emberBOT
manic cradle
sorry ok so I check both external_account and issuing capabilities
yes
acct_1PhlhlQ8LAeqi9YM
radiant quarry
It doesn't look like there are any requirements due at the moment, but (like the message says) those requirements could be due in the future. Until then though, you should be able to payout their balance
manic cradle
right I am just preemptively thinking I might have the user fill out any of the requirements currently_due or eventually_due to avoid disruption
are those requirements of 'external_accounts' capability , or requirements for 'issuing' capability?
radiant quarry
Those are requirements for both
manic cradle
got it - and if I show the user the account onboarding component - will they be able to edit/ add those details from there?
if they have alreayd created an account and have requirements
radiant quarry
Yes, though you would use the account_update parameter: https://docs.stripe.com/api/account_links/create#create_account_link-type
That's for existing accounts
manic cradle
oh I do not use an account link - just an account session and the embedded components
is there no way to do this with embedded components ?
radiant quarry
Ahhh, okay. Just a moment
Gotcha, okay so yeah. With embedded components you can just redirect them to onboarding as you mentioned already
manic cradle
ok thanks
what is the name of the capability I use for external accounts
I tried to retreive external_account and external_accounts but that doesnt exist
radiant quarry
Payout capabilities are implicit with the account, meaning they can't be requested or unrequested from the API. They can be disabled due to unresolved requirements, but you don't need to worry about requesting them.
You can use the payouts_enabled attribute on the Account object to check if you can pay out to an external account: https://docs.stripe.com/api/accounts/object#account_object-payouts_enabled
drifting emberBOT
manic cradle
ok sorry I am a bit confused.
I check the requirements currently due or eventually due for the issuing capability and send them to the onboarding component if not empty.
But for payout I should not check these?
hoary sun
Taking over this thread, catching up now
I'd recommend checking both currently due and eventually due requirements on the account itself irregarding what the capability is. Some requirements can be needed across multiple capabilities and they should be completed
manic cradle
ok since I am creating connected accounts strictly for issuing and then also being able to withdraw from the issuing balance back to the external account.
will checking the requriements for the 'issuing' capability suffice?
when I cerate the account they go through an embedded onboardign on our page with the external account collection set to true
hoary sun
Checking requirements for issuing capability isn't sufficient. If there is any pending requirements, they should be completed regardless which capability it is for
manic cradle
ok sorry I create the acccount with
transfers: {
requested: true,
},
card_issuing: {
requested: true,
},
us_bank_account_ach_payments: {
requested: true,
}
so should I check all these capabilities or like you mentioned this would not suffce?
hoary sun
To check whether there is any pending requirements, requirements hash should be checked, not the capability hash: https://docs.stripe.com/api/accounts/object#account_object-requirements
requirements will also include the requirements about payout which is not part of the capabillity.
manic cradle
ok thank you.
hoary sun
No problem! Happy to help 😄
manic cradle
sorry for the confusion I was reading the connect isusing doc and it said check the capability requirements and then I got confused by what you were saying on account requirements
hoary sun
The requirements hash will contain the requirements for both issuing and account itself. requirements are not categorised by the capability, but connected account as a whole. A requirement can complete multiple capabilities and account functions such as payout. Completing all requirements will prevent that connected account from being paused in a specific flow
manic cradle
great thank you so much.
also I wanted to confirm when I create a bank account token and a source - this will automatically initiate the microdeposits from stripe to the bank account right?
hoary sun
If a bank account and source is collected manually, then there won't be verification such as microdeposit. I'd recommend using Financial Connections for collecting bank account details, which helps to verify the bank account: https://docs.stripe.com/connect/payouts-bank-accounts
manic cradle
sorry looking at this guide:
hoary sun
Let me double check
For issuing fund pulling using bank account token and a source to create an external account, there will be microdeposits automatically: https://docs.stripe.com/issuing/connect/funding?issuing-funding-type=us-pull-funding#collecting-your-users’-information
For paying out to an external bank account, then I'd recommend using Financial Connection: https://docs.stripe.com/connect/payouts-bank-accounts
manic cradle
oh for payouts to an external accout I just call the payout method and it pays out to the default bank account they added during the embedded onboarding component
and if they want it to go to another account they can manage their account and change the payout account there
hoary sun
This looks right to me if you use embedded onboarding component to collect the bank account for payout
manic cradle
ok yes and for account management too.
manic cradle
I havent received the micodeposits yet for accounts I added yesterday - should I expect them tomororw?
hoary sun
Is it in test or live mode?
manic cradle
live
hoary sun
For live mode microdeposit, I'd recommend checking with Support https://support.stripe.com/contact as we mainly help with technical questions in this channel and don't have the necessary expertise in this topic
manic cradle
ok thank you