Stripe | Financial Infrastructure to Grow Your Revenue

Stripe | Financial Infrastructure to Grow Your Revenue

4466 articles

Adds the customer account property to v1 APIs for Accounts v2 interoperability

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.

Command Line

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_account 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.

Changes

ParameterChangeResources or endpoints
customer_accountAddedBilling. CreditBalanceSummary Billing. CreditBalanceSummary#retrieve Billing. CreditBalanceTransaction#list + 63 more Billing. CreditGrant Billing. CreditGrant#create Billing. CreditGrant#list BillingPortal. Session BillingPortal. Session#create CashBalance Checkout. Session Checkout. Session#create Checkout. Session#list ConfirmationToken. payment_method_preview CreditNote CreditNote#list Customer CustomerBalanceTransaction CustomerCashBalanceTransaction CustomerSession CustomerSession#create Discount FinancialConnections. Account#list. account_holder FinancialConnections. Account. account_holder FinancialConnections. Session#create. account_holder FinancialConnections. Session. account_holder Invoice Invoice#create Invoice#create_preview Invoice#list InvoiceItem InvoiceItem#create InvoiceItem#list PaymentIntent PaymentIntent#create PaymentIntent#list PaymentIntent#update PaymentMethod PaymentMethod#attach PaymentMethod#list PromotionCode PromotionCode#create PromotionCode#list Quote Quote#create Quote#list Quote#update SetupAttempt SetupIntent SetupIntent#create SetupIntent#list SetupIntent#update Subscription Subscription#create Subscription#list SubscriptionSchedule SubscriptionSchedule#create SubscriptionSchedule#list TaxId TaxId#create. owner TaxId#list. owner TaxId. owner required → optional Identity. VerificationSession Identity. VerificationSession#create Identity. VerificationSession#list PaymentMethod#list

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
  • If you don’t use an SDK, update your API requests to include Stripe-Version: 2025-12-15. clover
  1. Upgrade the API version used for webhook endpoints .
  2. Test your integration against the new version.
  3. If you use Connect, test your Connect integration .
  4. In Workbench, perform the upgrade . You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Last verified 2026-09-24
Connect platforms can now use Accounts v2 to manage connected accounts and customersAccounts v2 now always returns the responsibilities field when the defaults field is included

Is this helpful?