Standard vs. Express vs. Custom account types for Stripe Connect

In this series, you’ll learn all about Stripe Connect, the set of Stripe APIs and tools for building a platform or marketplace to route payments between multiple parties.
在这个系列中，您将全面了解 Stripe Connect，这是一套 Stripe API 和工具，用于构建平台或市场以在多方之间路由支付。

If you’re using Stripe Connect, you’ll need to create an account (called a “connected account”) for each user who collects payments with your platform. You’ll do this every time a user signs up for your platform. The type of account you choose for your user will determine the development work required for the Stripe integration you need to build (options range from Stripe-hosted to completely custom) and what operational responsibilities you’ll have (like handling chargebacks and supporting your users). It’s possible to mix and match account types for your platform if you are solving for different use-cases or segments. There are three account types to choose from with Connect, each designed for different needs: Standard, Express, and Custom. We’ll first compare and contrast the integration effort and operational overhead, then close with some recommendations.
如果您使用 Stripe Connect，您需要为每个通过您的平台收款的用户创建一个账户（称为“连接账户”）。每当有用户注册您的平台时，您都需要这样做。您为用户选择的账户类型将决定您需要构建的 Stripe 集成所需的开发工作（选项范围从 Stripe 托管到完全自定义），以及您将承担的运营责任（如处理退款和支持您的用户）。如果您针对不同的用例或细分市场，您的平台可以混合搭配不同类型的账户。Connect 提供三种账户类型供选择，每种都设计有不同的需求：Standard（标准）、Express（快速）和 Custom（自定义）。我们将首先比较和对比集成工作和运营开销，然后给出一些建议。

:moneybag:Keep in mind, there is an additional cost for using Express or Custom account types.

Integration effort

When it comes to integration effort, Standard and Express accounts are the most straightforward options with Standard accounts requiring the least amount of work to integrate. However, if you want more control over the user experience, you may want to consider Custom accounts. While Custom accounts allow you to whitelabel the entire experience, they require significantly more development effort to implement.
当涉及到集成工作时，Standard 和 Express 账户是最直接的选择，其中 Standard 账户需要的集成工作量最少。然而，如果你想要更多地控制用户体验，你可能会考虑使用 Custom 账户。虽然 Custom 账户允许你对整个体验进行白标化，但它们需要更多的开发工作来实施。

Here are more details about the integration requirements for each account type:

Onboarding

Stripe-hosted onboarding supports all account types. The hosted onboarding integration requires at least two API calls.
Stripe 托管的入驻支持所有账户类型。托管入驻集成至少需要两个 API 调用。

1. Create a connected Account. Note that you can pre-populate many account details if you like the user’s website, support phone number, mailing address, etc. that way, they don’t need to re-enter those details when onboarding.
   创建一个关联账户。请注意，如果你愿意，你可以预填充许多账户详细信息，比如用户的网站、支持电话号码、邮寄地址等，这样他们在入驻时就不需要重新输入这些详细信息。

const account = await stripe.accounts.create({type: ‘standard’});

1. Create an Account Link that redirects the user through the Stripe hosted onboarding flow:

const accountLink = await stripe.accountLinks.create({
  account: account.id,
  refresh_url: 'https://example.com/reauth',
  return_url: 'https://example.com/return',
  type: ‘account_onboarding’,
});
// redirect to accountLink.url

Connect Onboarding makes it easy to onboard merchants to your platform by providing conversion-optimized, pre-built user interfaces. This means you can easily get your merchants set up without having to worry about the complexity of building your own identity verification and onboarding flows. Plus, Connect Onboarding helps you minimize compliance and operational issues.
Connect Onboarding 通过提供优化转化的、预建的用户界面，使得商户接入您的平台变得简单。这意味着您可以轻松地设置您的商户，而不必担心构建自己的身份验证和接入流程的复杂性。此外，Connect Onboarding 还有助于您最小化合规和运营问题。

I recommend using Connect Onboarding for all account types. It’s worth calling out that you can technically build your own custom onboarding flow for Custom accounts and use the API to update details about the account and check for a list of additional verification requirements. Localizing a custom form and nailing all of the identity verification flows for multiple countries is quite a heavy lift so unless you have significant engineering resources, I would default to using Connect Onboarding.
我推荐对所有账户类型使用 Connect Onboarding。值得一提的是，您技术上可以为 Custom 账户构建自己的定制接入流程，并使用 API 更新有关账户的详细信息以及检查额外的验证需求列表。本地化定制表单并为多个国家实现所有身份验证流程是一项相当繁重的任务，所以除非您有充足的工程资源，否则我会默认使用 Connect Onboarding。

Automatic updates for new compliance requirements

Global compliance requirements and rules do change over time. For Standard and Express accounts, Stripe will proactively reach out and collect information about your accounts whenever requirements change.
全球合规要求和规则会随时间变化。对于 Standard 和 Express 账户，Stripe 将主动联系并收集您的账户信息，每当要求发生变化时。

If you’re using Custom account types with a bespoke onboarding flow and haven’t integrated with Connect Onboarding, you’ll need to invest development resources to make updates as compliance requirements change over time. However, if you use Connect Onboarding for Custom accounts, you can easily collect onboarding and verification information from your users and save yourself the hassle of constantly updating your onboarding form. Plus, Connect Onboarding can help you stay up-to-date with the latest compliance requirements without any extra effort on your part. Just make sure to follow best practices for communicating changes to your users, as outlined in the guide for Custom accounts.
如果您正在使用自定义账户类型并且拥有定制的入职流程，且尚未与 Connect 入职集成，那么您将需要投入开发资源随着合规要求的变化而更新。然而，如果您为自定义账户使用 Connect 入职，您可以轻松地从用户那里收集入职和验证信息，避免不断更新您的入职表单的麻烦。此外，Connect 入职可以帮助您不费吹灰之力地保持最新的合规要求。只需确保遵循最佳实践来向用户通报变更，如自定义账户指南中所述。

Integration effort is one the most heavily weighted factors when deciding which Stripe Connect account type to choose. Most startup and growth companies have the bandwidth and resources to implement and maintain Standard and Express accounts. If you don’t have a team of engineers to dedicate significant bandwidth to maintaining a Custom integration, I recommend Standard or Express.
集成工作量是决定选择哪种 Stripe Connect 账户类型时最重要的因素之一。大多数初创和成长型公司都有足够的带宽和资源来实施和维护标准和快速账户。如果您没有一个工程师团队来专门投入大量带宽来维护自定义集成，我推荐使用标准或快速账户。

Operational responsibilities

Another important consideration is who handles the operational responsibility day to day. For instance, are you the platform liable for fraud and disputes related to payments for a connected account? What type of dashboard can the connected account access to view payments, issue refunds, handle disputes, and update their information? Who is responsible for supporting connected account users when questions arise? Some of the following details differ depending on the charge type (direct vs destination) which we’ll cover in another article. Just know that one charge type may have different operational requirements than another charge type.
另一个重要的考虑因素是谁每天处理运营责任。例如，你作为平台是否对连接账户相关支付的欺诈和争议负责？连接账户可以访问哪种类型的仪表板来查看支付、发放退款、处理争议以及更新他们的信息？当问题出现时，谁负责支持连接账户用户？以下一些细节根据收费类型（直接 vs 目的地）的不同而有所不同，我们将在另一篇文章中讨论。只需知道一种收费类型可能与另一种收费类型有不同的运营要求。

Fraud and dispute liability

If you’re trying to decide between Standard and Express accounts, this is likely the tie breaker.

For Standard accounts, the connected account owner (your user) is responsible for dealing with fraud and disputes*. For Express and Custom accounts, you as the platform are ultimately responsible for dealing with fraud and disputes.
对于标准账户，连接账户所有者（你的用户）负责处理欺诈和争议*。对于 Express 和 Custom 账户，你作为平台最终负责处理欺诈和争议。

Understanding the dispute process and how to handle fraud is part of any online business. Standard accounts are more suited for experienced online businesses, whereas Express accounts are ideal for businesses at any level of experience.
理解争议处理过程以及如何处理欺诈是任何在线业务的一部分。标准账户更适合有经验的在线业务，而快捷账户则适合任何经验水平的业务。

• this may shift depending on the charge type used.

Dashboard access

Standard accounts are conventional Stripe accounts where the account holder (your user) is able to log in to the Dashboard and can process charges on their own. If you want to obfuscate the relationship between the connected account holder and their end user for any reason, Standard is likely not a good fit.
标准账户是传统的 Stripe 账户，账户持有者（您的用户）可以登录仪表板，并可以自行处理费用。如果您出于任何原因想要隐藏连接账户持有者与其最终用户之间的关系，标准账户可能不是一个好选择。

Express accounts can only use the Express Dashboard, a simplified Stripe-hosted interface. From the Express Dashboard, your users can view their available balance, see upcoming payouts, and track their earnings in real time. The Express Dashboard does not have all of the same features as the Standard Dashboard.
快捷账户只能使用快捷仪表板，这是一个简化的 Stripe 托管界面。从快捷仪表板，您的用户可以查看他们的可用余额，查看即将到账的款项，并实时跟踪他们的收入。快捷仪表板没有标准仪表板的所有功能。

Custom accounts do not have access to a Stripe-hosted dashboard. You’ll need to build custom interfaces into your application for your users to handle any operational tasks related to running their business.
自定义账户无法访问 Stripe 托管的仪表板。您需要为您的应用程序构建自定义界面，以便您的用户处理与经营业务相关的任何操作任务。

User support

All support questions about a Custom connected account are handled by you, the platform. For Standard and Express accounts, some questions can be answered by Stripe and others will be handled by the platform. For instance, as identity verification requirements shift and change, Stripe will proactively reach out to your users to ensure the information on file stays compliant with local regulations.
关于自定义连接账户的所有支持问题都由您这个平台来处理。对于标准和快速账户，一些问题可以由 Stripe 回答，其他问题将由平台处理。例如，随着身份验证要求的变化和调整，Stripe 将主动联系您的用户，确保档案中的信息符合当地法规的合规性。

Recommendations

Absent a compelling reason for a bespoke integration and lots of resources to build and maintain a Custom Connect integration, I would default to either Standard or Express. Assuming the platform I’m building is open to handling fraud and disputes, the platform decision between Standard and Express comes down to the relationship I expect users to have with end customers. Will my users, the owners of the connected accounts, need a long standing relationship with their customers or will their relationship be one-off, and transactional in nature? If so, do I expect my customer base to be savvy enough (or teachable enough) to handle fraud and disputes and trusted with the ability to charge the end customer manually. If I’m working with online business savvy folks who maintain long-running relationships with their end customers, I’d choose Standard. If I’m working with any internet user who has a one-off relationship with end customers or if I want to prevent them from charging end customers, then I’d lean towards Express.
除非有充分的理由进行定制集成，并且有大量资源来构建和维护 Custom Connect 集成，否则我会默认选择 Standard 或 Express。假设我正在构建的平台愿意处理欺诈和争议，那么在 Standard 和 Express 之间的平台决策归结为我期望用户与最终客户之间的关系。我的用户，即连接账户的所有者，是否需要与他们的客户保持长期关系，还是他们的关系是一次性的，且本质上是交易性的？如果是这样，我是否期望我的客户群足够精明（或可教育）来处理欺诈和争议，并且信任他们有能力手动向最终客户收费。如果我与那些对在线业务精通并与最终客户保持长期关系的人合作，我会选择 Standard。如果我与那些与最终客户只有一次性关系的任何互联网用户合作，或者如果我想阻止他们向最终客户收费，那么我会倾向于选择 Express。