#dev-in-need_docs

1 messages · Page 1 of 1 (latest)

tepid socketBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1259926512212377690

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

arctic hawk
#

No. For onboarding, the Connect Account owner should be able to add their external account using the Stripe-hosted onboarding portal. There's no need to build a customer form for that

sturdy tangle
#

how do they then verify the account if its entered manually?

#

they are able to access and manage their business information at any time from our application, and I noticed when I went back to my test business form they could link additional external accounts. What is the process for them to verify with microdeposits then? Do they go back to the business information form to do so?

arctic hawk
sturdy tangle
#

ahh ok

arctic hawk
#

Correct

sturdy tangle
#

ok thank you.

#

and I can use the original linked account?

#

for example the account that was added during onboarding - I receive when I call the listexternalaccounts route - this accoutn I can still utilize and have them verify with microdeposits since the status is "new"

arctic hawk
#

Correct

sturdy tangle
#

ok great. Appreciate your help!

sturdy tangle
#

do I still create the bank account token and then the source?

arctic hawk
#

And the sources API is deprecated specifically for the Payment Intents/Charges workflows. I believe it's still standard for the methods mentioned in these Issuing docs