#hoffemberg_api
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/1284174767674622095
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐ you're spot on! The "status" of a Connected Account is a dashboard-only status that isn't exposed in the API.
charges.enabled and payouts.enabled are key fields to check to ensure the account can process payments. If those are false you'll want to look into requirements and possibly future_requirements to identify what is still missing. I think we have a doc that may break this down a bit more, let me see if I can find that.
The refresh URL for an Account Link is important if the link has expired, already been visited, or runs into an unexpected problem that renders it invalid. Then your refresh URL is hit to get a new Account Link for your user.
Ah, this is what I was thinking of where we give a bit better breakdown of what each dashboard status means, and discuss some of the fields to look at for each status:
https://docs.stripe.com/connect/dashboard#status-badges
Okay, thanks, just wanted to make sure. Regarding the refresh URL, is a possible scenario that a user is in the process of doing the onboarding, and then they go AFK for a while, and then need to come back to it? And then they're timed our or they logged off, and they try to use the url again?
And will their progress be saved with a new url and they won't have to start over?
Yup, that's one scenario, if they try to use the same account link URL more than once. There's also the case where they don't visit the link before the expires timestamp on the account link passes:
https://docs.stripe.com/api/account_links/object#account_link_object-expires_at
Their onboarding progress is saved after every step if I'm recalling correctly. So I'm pretty sure when they return to the onboarding process later the details they had already provided will be retained.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Okay, thanks so much!
Any time!