#L0rdandBooz

1 messages · Page 1 of 1 (latest)

blissful etherBOT
viral bolt
#

for further context on what I mean by connect onboarding

hardy lake
#

Financial connections is only available in US. If your platform and connected accounts are not in US, then bank account ownership can't be verified

viral bolt
#

is it necessary to? I was already using that financial connections tool through the API in order to create a payment method token but for some reason it doesn't satisfy that external account requirement

hardy lake
#

for some reason it doesn't satisfy that external account requirement
What do you mean? The financial connections here refers to payout bank account, not the payment method collection for charges

blissful etherBOT
viral bolt
#

I'd use stripe financial connections in order to create a bank account PM token then inbound / outbound transfer from a financial account using it. To me that feels like an external account but it doesn't satisfy that external account requirement.

#

As of 3/4 days ago I'm no longer able to get treasury enabled on my custom connect accounts without that external_account so I'm trying to figure out the best way to go about it.

wicked gazelle
#

if your question is whether you need to verify the bank account - no, it's not a requirement to do so

viral bolt
#

Ok but would I still be able to inbound outbound transfer with it? My concern isn't necessarily about getting rid of this requirement it's about getting rid of it and allowing my customers to inbound outbound transfer from it.

#

I don't want them to need to link the same bank account twice.

#

And will this transfer it to their financial account so they can spend from it with their issuing cards?

#

Here's an example of one of my inbound transfer api calls

            inboundTransfer = await stripe.treasury.inboundTransfers.create(
                {
                    origin_payment_method: req.body.paymentMethod,
                    financial_account: req.body.financialAccountID,
                    amount: req.body.transferAmount,
                    currency: 'usd',
                    description: req.body.description,
                    // statement_descriptor: req.body.memo,
                },
                {stripeAccount: req.body.connectAccountID}
            );
hardy lake
#

Let's step back a bit. External account is meant for payout purpose. From your code, this is about treasury which has nothing to do about external account for payout

#

Can you share what your use case is? Are you referring to payout account or treasury transfer?

viral bolt
#

Ah I see. I need a treasury transfer to my financial account. The issue is my treasury isn't enabled until I satisfy this external account requirement

#

requirements: {
alternatives: [],
current_deadline: null,
currently_due: [ 'external_account' ],
disabled_reason: 'requirements.past_due',
errors: [],
eventually_due: [ 'external_account' ],
past_due: [ 'external_account' ],
pending_verification: []
},

hardy lake
#

Can you share which integration doc are you following?

viral bolt
#

It feels like that guide was updated or I grabbed you the wrong one. Let me try and find a different one.

hardy lake
viral bolt
#

Yes that's the one!

hardy lake
viral bolt
#

There is nothing within that doc that I am stuck at. I had it all working perfectly as far as creating a payment method for a stripe inbound transfer. For whatever reason, newly onboarded customers are no longer able to do an ACH transfer without fulfilling that external account criteria. If I am creating an external account then I don't want my customers to need to create the PM token as well. How do I combine these two for simplicity sake of my user? Ultimately the funds need to end up in the treasury financial account. How do I get to that point in the least amount of steps for my customers and I? Hopefully that all makes sense thank you for your help so far

https://stripe.com/docs/api/external_account_bank_accounts/create#account_create_bank_account-external_account-object

hardy lake
#

For whatever reason, newly onboarded customers are no longer able to do an ACH transfer without fulfilling that external account criteria.
Can you share the request ID (req_xxx) of the error that newly onboarded customers are no longer able to do ACH transfer without fulfilling external account criteria?

viral bolt
#

req_dFun9sjK9UgRil

#

req_EKbTfQjgcaH4om

#

Two different attempts from same person

#

It seems like the external account can be created with bank account details and you don't necessarily need to use a btok for it: https://stripe.com/docs/api/external_account_bank_accounts/create .

I am able to use a verified bank account on an external account on a connect account or a payment method token according to this guide: https://stripe.com/docs/treasury/moving-money/financial-accounts/into/inbound-transfers#:~:text=Inbound transfers move money from,the Same Day ACH capability.

How do I set up that verified external account?

#

Does all of that seem like reasonable takeaways from those guides or am I wrong?

hardy lake
#

Thanks for sharing the request ID. Can I suggest you writing into Stripe Support https://support.stripe.com/contact and share the request ID that requires with fulfilling the external criteria (newly onboarded connected account) and the one doesn't (old connected account)? I'm not too familiar with treasury and the minimal steps to collect the bank account information for both payout external account and treasury external account. Support team will be able to help you better than I can

viral bolt
#

Sounds good thanks so much for your time!