# Create connected accounts with Managed Risk

Create connected accounts where Stripe manages credit and fraud risk and assumes losses from unrecoverable negative balances.

Create connected accounts with [**defaults.responsibilities.losses\_collector**](https://docs.stripe.com/api/v2/core/accounts/create.md?rds=1#v2_create_accounts-defaults-responsibilities-losses_collector) set to `stripe` when your platform plans to use [Managed Risk](https://docs.stripe.com/connect/risk-management/managed-risk.md). With Managed Risk, Stripe manages credit and fraud risk and assumes losses from unrecoverable negative balances on connected accounts. This configuration is recommended for SaaS platforms, as well as any platforms that want Stripe to manage risk and can use direct charges.

## Code sample

The following code sample creates a connected account with Stripe as the fees collector, Stripe as the losses collector, and the full Stripe Dashboard, to enable you to get started with minimal additional setup. Adjust the parameters as needed for your particular use case.

If you use a [restricted API key](https://docs.stripe.com/keys.md#create-restricted-api-key) for live-mode requests, grant it the `v2_account_storer_write` permission.

```cli
stripe v2 core accounts create \
  --contact-email="jenny.rosen@example.com" \
  --dashboard=full \
  --identity.country=US \
  --defaults.responsibilities.fees-collector=stripe \
  --defaults.responsibilities.losses-collector=stripe \
  --configuration.merchant.capabilities.card-payments.requested=true
```

If you received an account-creation error because your request had your platform responsible for negative balances, update your integration:

- Use Accounts v2 for new Connect integrations; it provides configurable account behavior and supports newer Connect capabilities.
- If you were using the legacy `type` parameter with Accounts v1, Accounts v2 doesn’t use `type`. Instead, configure dashboard access, responsibilities, and supported configurations.
- Set **defaults.responsibilities.losses\_collector** to `stripe`.
- Retry account creation with the updated configuration.

If you were originally trying to create an `express` type account, set [**dashboard**](https://docs.stripe.com/api/v2/core/accounts/create.md?rds=1#v2_create_accounts-dashboard) to `express`. If you were originally trying to create a `custom` type account, set [**dashboard**](https://docs.stripe.com/api/v2/core/accounts/create.md?rds=1#v2_create_accounts-dashboard) to `none`. Then, refer to [Fee behavior on connected accounts](https://docs.stripe.com/connect/direct-charges-fee-payer-behavior.md) to determine what to set for the fees collector.

> #### Preview API version required with the Express Dashboard
> 
> Combining Express Dashboard access with Managed Risk is in [public preview](https://docs.stripe.com/release-phases.md). To create this type of account with the Stripe CLI, set `dashboard` to `express` and pass the current preview API version:
> 
> ```cli
stripe v2 core accounts create \
  --stripe-version 2026-08-26.preview \
  --contact-email="jenny.rosen@example.com" \
  --dashboard=express \
  --identity.country=US \
  --defaults.responsibilities.fees-collector=stripe \
  --defaults.responsibilities.losses-collector=stripe \
  --configuration.merchant.capabilities.card-payments.requested=true
```

## Additional requirements for Managed Risk

Managed Risk requires [direct charges](https://docs.stripe.com/connect/direct-charges.md) and has specific onboarding and account experience requirements. Review the [Managed Risk requirements](https://docs.stripe.com/connect/risk-management/managed-risk.md#availability) before updating your integration.

Onboard connected accounts with [Stripe-hosted onboarding](https://docs.stripe.com/connect/hosted-onboarding.md) or [embedded onboarding](https://docs.stripe.com/connect/embedded-onboarding.md). If you aren’t using the full Stripe Dashboard or Express Dashboard, add the embedded [Notification Banner](https://docs.stripe.com/connect/supported-embedded-components/notification-banner.md) and [Account Management](https://docs.stripe.com/connect/supported-embedded-components/account-management.md) components so connected accounts can receive notifications and update their business information.

## If your platform plans to assume loss liability

Use `application` as the losses collector only when your platform has chosen to both manage the associated credit and fraud risk, and to assume losses from unrecoverable negative balances. This configuration supports platforms with previous experience in this domain, and the specific need for funds flows such as separate charges and transfers or destination charges.

To use this configuration, visit your [Platform profile](https://dashboard.stripe.com/settings/connect/platform-profile) settings to complete the loss-liability acknowledgement and any applicable verification requirements.