Adds the customer account property to v1 APIs for Accounts v2 interoperability
What’s new
Adds the customer_account property, which enables Connect platforms and marketplaces that use Accounts v2 to reference payments that they collect from connected accounts or customers. This property is available in several API v1 endpoints, such as Payment Intents and Invoices.
For example, you can use the Setup Intents API to save an account’s payment credentials for future payments. In this example, the Account must be configured as a customer.
curl https://api.stripe.com/v1/setup_intents \ -u "${API_KEY}" \ -H "Stripe-Version: 2025-12-15.clover" \ -d "payment_method_types[]=stripe_balance" \ -d "payment_method_data[type]=stripe_balance" \ -d confirm=true \ -d customer_account=acct_1234 \ -d usage=off_session
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, synchronizing 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.
Pass your user’s account ID in the customer_ property for APIs that collect or track payments.
No change is required if your integration uses Customers v1 and the customer property. If you’re interested in using the Accounts v2 API for new or existing connected accounts, register in the Dashboard.