Connect platforms can now use Accounts v2 to manage connected accounts and customers
What’s new
The Accounts v2 API is now available for new Connect users to represent both their connected accounts and customers across Stripe. You can map all of your user’s activity to a unified Account object that can be configured as a customer, merchant, and/or recipient.
Learn more about building Connect with the Accounts v2 API.
Impact
Platforms and marketplaces on Connect often charge their connected accounts for services they provide. Previously, you used the Accounts v1 API and Customers v1 API to create two objects that represent a single user. This split representation meant collecting KYC twice, synchronising data between the two objects, and storing multiple IDs for the same user.
You can now use the Accounts v2 API to create a single identity to represent your user across Stripe. This improves onboarding conversion by sharing KYC across your user’s customer and connected account identities, so Connect users don’t have to build duplicate representations and custom relationship logic.
We recommend the Accounts v2 API integration path when building new Connect integrations.
Existing platforms don’t need to change their integration. If you’re interested in using the Accounts v2 API for new or existing connected accounts, register in the Dashboard. For example, you may want to use an Account as a Customer to collect recurring SaaS fees with balance payments.