Configure the behavior of connected accounts

You define the interactions between your platform, connected accounts, and Stripe, such as funds flows and loss liability, by configuring your connected accounts. Set up your integration to configure them by specifying values for certain properties when it creates the corresponding Accounts v2 objects. For example, properties in the defaults.responsibilities hash assign liability for negative balances on your connected accounts and specify how Stripe collects payment fees.

The values you assign to your connected account properties also affect other aspects of your integration. For example, responsibility for verifying identity information is assigned to Stripe or your platform based on negative balance liability and connected accounts’ access to Stripe Dashboards.

Set responsibilities

You must define defaults.responsibilities properties when you add the Merchant configuration to an account. You can’t update their values later.

Responsibilities are subject to the following restrictions:

• If you set losses_collector to application, then you must also set fees_collector to application.
• If you use destination charges with an Account, we recommend that you set both losses_collector and fees_collector to application.

For more information about supported configurations, see Integration recommendations.

Set Dashboard access

You must set the dashboard property value (if its existing value is null) when you add the Merchant configuration to an account. You must also set the dashboard value (if its existing value is null) when you request the stripe_transfers feature for the Recipient configuration on an account. Choose from the following values:

• express: The connected account can access the Stripe Express Dashboard, which offers limited functionality. You can customize its appearance with your platform’s branding.
• full: The connected account can access the full Stripe Dashboard. The full Stripe Dashboard lets your connected accounts view and manage their finances and reports.
• none: The connected account can’t access either Stripe Dashboard. Your platform must provide all Stripe-related functionality.

Regardless of the dashboard setting, your platform can use Connect embedded components to provide your connected accounts with similar functionality in a custom interface.

Dashboards are subject to the following restrictions:

• If you set dashboard to express, then you must also set both losses_collector and fees_collector to application.
• If you set dashboard to full, then you must also set both losses_collector and fees_collector to stripe.

For more information about supported configurations, see Integration recommendations.

Collect Know Your Customer (KYC) requirements

Responsibility for collecting KYC requirements is based on the defaults.responsibilities.losses_collector and dashboard values. In most configurations, Stripe is responsible for collecting KYC requirements from your connected accounts. Your platform is responsible only when you set defaults.responsibilities.losses_collector to application and dashboard to none. You can check the configuration by looking at defaults.responsibilities.requirements_collector, which can be stripe or application.

Accounts v1 controller property map

The settings described in this document correspond to Accounts v1 controller properties as follows: