#elektrababian_unexpected
1 messages · Page 1 of 1 (latest)
👋 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/1349417085356478636
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi 👋
It is expected that if your Connected Account user chooses to manually input their account information, we will not create a Financial Connection Account. In this case we fall back to creating a normal Bank Account.
We will not return any Financial Connections Account data in that case.
In that case, all we create is the External Account
Shouldn't I expect to see the external account get created in that connected account's logs then? there's no information on an external account in the logs
Do you have the account ID?
Yes, it's acct_1KoWdqQhRgtBVaXY
Also if a user inputs their bank account information manually is it expected they then would recieve microdeposits in their account?
Also if a user inputs their bank account information manually is it expected they then would recieve microdeposits in their account?
Yes, that is our fallback verification method
With respect to the Account, I can see the external bank account created for it.
I can see the external account when I did the api call from the doc you shared, but i dont see it in the connected account logs
Do you know how the user is expected to verify the micro deposits once they land in their account for the manual verification flow?
This connected account has been created since 2022 so I am not able to page back to the logs but it is likely the external account was created as part of the account.created event.
Do you know how the user is expected to verify the micro deposits once they land in their account for the manual verification flow?
It uses some of the same approach as we do for ACH direct debits with micro-deposits we document here
Essentially:
Stripe notifies your customer via this email when the deposits are expected to arrive. The email includes a link to a Stripe-hosted verification page where they can confirm the amounts of the deposits and complete verification.
We send an email with a form for them to verify the amounts
Thank you for that information.
Once a Stripe External Bank account has it's micro deposits verified, if we wanted to create a PaymentIntent to the connected account's payments balance from that external bank account, would we just need to create a payment method attached to the stripe external bank account record and use that to create the payment intent?
Hi, taking over as my teammate needs to step away. Let me catch up.
What you're asking is not supported. You would need to collect the payment method type and create a PaymentIntent using the pm_ id to charge them.
Alternatively, you can just create Account Debits, https://docs.stripe.com/connect/account-debits to collect funds from the ConnectedAccounts's Stripe Balance since you're using Custom Connect.
Let me know what specific you may have after reviewing the above document.
How would you suggest sending funds from a connected account's stripe external bank account to the connected account's payments balance?
Please review https://docs.stripe.com/connect/account-debits#requirements
If a connected account has a negative balance, Stripe might auto-debit the external account on file, depending on what country the connected account is in. If the external account hasn’t been verified, the debit can fail.
Other than this, you can't just charge the external account for payments. You would need to collect the payment method and then charge that
Yeah that's what I was getting at earlier, we would need to create a payment method attached to the stripe record of the external bank account and then we could create a payment intent using that payment method right?
I do not know what this 'payment method attached to the stripe record of the external bank account ' means but yeah, you would need pm_ for that payment method and then pass that pm_ when creating the PaymentIntent
Sorry I'm not being more clear here -- I'm essentially trying to replicate the flow we have in place where we use a connected account's stripe financial connections account to create a payment intent, but in this case the user would go through the manual verification flow so the stripe external bank account record is created instead of a stripe financial connections account. When I say attached to the external bank account, I'm referring to how in the SFCA flow with payment method creation we set the us_bank_account on the payment method to the financial_connections_account so I was asking if there's a way to do something like that for the stripe external bank account record instead
Yeah, you still need to collect the same payment method from them for PaymentMethods to charge them latet using the PaymentIntent. They will still need to verify it because there is no way to copy a verified external account as a payment method
Are you still here?
When you say, 'they will still need to verify it' can you clarify what you mean? would that entail microdeposits?