When you upgrade to Stripe API version 2026-09-30.endive (or an SDK major that pins it), creating a v2 Account Link with a configurations parameter in use_case.account_onboarding or use_case.account_update fails
Took effect · Stripe API 2026-09-30.endive — v2 Account Links create: use_case.account_onboarding/account_update configurations removed
Reviewed against the vendor source on Oct 2, 2026 (AI-assisted review). Key facts are re-checked against the source daily.
What changes
Stripe now determines which configurations (such as customer, merchant or recipient) need onboarding, so the parameter was removed from both use cases on v2 Account Link create and from the Account Link object. Requests that include configurations return an error on 2026-09-30.endive or later.
Breaking: Calls fail after this date.
What to do
Remove configurations from use_case.account_onboarding and use_case.account_update when creating v2 Account Links before moving to 2026-09-30.endive; Stripe picks the configurations to onboard.
Counts only in files that mention stripe + account_onboarding or stripe + account_update or stripe + accountonboarding or stripe + accountupdate; repos that depend on stripe 16.x (pypi) or stripe 23.x (npm) or stripe 20.x (rubygems) or github.com/stripe/stripe-go/v87 87.x (go) or stripe/stripe-php 22.x (packagist); or repos that mention 0.endive or 1.endive or 2.endive or 3.endive or 4.endive or 5.endive or 6.endive or 7.endive or 8.endive or 9.endive or stripe==16 or stripe>=16 or stripe~=16 or stripe = "^16 or stripe = "~16 or stripe = ">=16 or stripe = "==16 or stripe = "16 or "stripe": "^23 or "stripe": "~23 or "stripe": "23 or stripe@^23 or stripe@23 or stripe-go/v87 or stripe (20. or gem 'stripe', '~> 20 or gem "stripe", "~> 20 or stripe-java:34. or Stripe.net" Version="53 or "stripe/stripe-php": "^22 or "stripe/stripe-php": "~22 or "stripe/stripe-php": "22 or stripe@npm:^23 or stripe@npm:23 (including dependency manifests).