zen_best-practices

[kindred lodge]

👋 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/1382069467181482166

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

[olive basalt]

Hello
I assume you're referring to: https://docs.stripe.com/api/account_links/create

Can you explain what you mean by "Explain requirements"
I'm not sure I fully grasp

[true path]

Apologies for the lack of details, it's been a bit confusing haha.

If I understand correctly with v1 accounts, in their "Standard" mode, us as the platform needs to provide information about requirements and the current status of the account, right?

And by "explain requirements" I explicitly mean present them to the customer that they are missing certain things and must log into stripe to fix them

[olive basalt]

If I understand correctly with v1 accounts, in their "Standard" mode, us as the platform needs to provide information about requirements and the current status of the account, right?
Not sure what you mean by standard mode 😅

What kind of connected accounts are you creating? Standard, Express OR Custom?

[true path]

Standard

[olive basalt]

Gotcha. So with Standard accounts, you'd use Stripe hosted onboarding (NOT API based onboarding) using Account Links
https://docs.stripe.com/connect/standard-accounts

[true path]

Ah, yes this is what I am trying to do.

I currently generate a link, provide it to the user, and they continue onboarding there.

What I am trying to understand is what happens after that. When the customer is redirected back to our platform, are we then responsible for displaying the current status of the account? Of the necessary requirements they still have due?

[olive basalt]

Yes. That's Step 4 and 5 in the doc I shared

[true path]

The account status I am currently using is coming from here: https://docs.stripe.com/api/accounts/object

The requirements I was referring to previously are a part of the requirements object here.

[true path]

Oh, OK so I really just need to check that value and display whether or not they are complete?

[olive basalt]

Correct, requirements parameter would tell you what's missing and then you can redirect the users back to a new Account Link (as explained in step 5)

[true path]

Are we required to present them with these specific requirements that they are missing?

Or should we simply be stating "There are unsatisfied requirements."

[olive basalt]

The latter. You aren't required to tell them that "hey, you're missing XYZ" as such

If you want to, then you can but you don't "have" to afaik

[true path]

Okay, that makes things significantly easier. Thanks.

Just to make sure I understand everything you've sent correctly:

1. We can view whether or not an account is ready to operate via the charges_enabled boolean on the Account object. If this is true: Their account is in good standing and ready to go. If this is false: Their account is not ready to operate.
2. We can view whether or not they have completed onboarding (not necessarily succeeded) via the details_submitted boolean on the object.
3. If charges_enabled is true and details_submitted is also true, then we do not need to provide them with an onboarding link.

Is this all correct?

[olive basalt]

1. Correct
2. Correct
3. Correct

[true path]

Thank you, the only thing I have left to ask about is regarding v1 versus v2 accounts.

We have always used v1 accounts in the past. Is it OK/best practice to continue using the "Standard" Stripe connect accounts, and the v1 APIs, or will this be deprecated sometime soon?

[olive basalt]

There are no deprecation plans for v1 so you can continue to use them 🙂

We do have a migration guide for v1 to v2 -> https://docs.stripe.com/connect/accounts-v2/migrate

But we also have a callout

[true path]

I will stay with v1 in this case, as all of our customers are currently using v1 objects and the vast majority are linking from existing accounts.

Thank you for the clarification.