Accounts v1 support for new Connect integrations

Learn when you might need to use the Accounts v1 API and how to enable it.

Use the Accounts v2 API for Connect

Stripe recommends the Accounts v2 API ( /the relevant part of the product) for most Connect integrations. It uses configurations to support multiple types of relationships that connected accounts have with your platform, and is interoperable with most v1 APIs. When using the Accounts v1 API, additional relationships require you to create additional objects representing your connected accounts.

For best practice, see Configure the behaviour of connected accounts.

When you might still need Accounts v1 support

Use the Accounts v2 API unless you need to use the v1 API for a specific reason.

Your integration might need to use the Accounts v1 API if it depends on functionality or behaviour that the Accounts v2 API doesn’t yet support. Use the v1 API only if you require a feature in the following list:

You must use Accounts v1 in the following cases:

• Using OAuth to authenticate connected accounts
• Signing connected accounts to a recipient service agreement
• To request or manage the following capabilities:
• treasury
• card _ issuing _ *
• deprecated capabilities such as legacy _ payments
• deprecated payment methods
• certain payment methods in public or private preview

If your platform still requires the Accounts v1 API, you can enable access in the Dashboard:

1. Open Accounts v1 support in the Dashboard ( Settings > Developers > API Policies > Accounts v1 Support ).
2. Click the Edit icon ( ) to open the edit panel.
3. Enable the feature for Test mode or sandboxes as desired, then click Save .
4. Retry your request to create an Account with the Accounts v1 API.