Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
Versioning
Changelog
    Overview
    Clover
    Basil
    Acacia
    Previous versions
Upgrade your API version
Upgrade your SDK version
Essentials
SDKs
API
Testing
Stripe CLI
Sample projects
Tools
Stripe Dashboard
Workbench
Developers Dashboard
Stripe for Visual Studio Code
Terraform
Features
Workflows
Event Destinations
Stripe health alertsFile uploads
AI solutions
Agent toolkit
Model Context ProtocolBuild agentic AI SaaS Billing workflows
Security and privacy
Security
Stripebot web crawler
Privacy
Extend Stripe
Build Stripe apps
Use apps from Stripe
Partners
Partner ecosystem
Partner certification
United States
English (United Kingdom)
  1. Home/
  2. Developer resources/
  3. Changelog/
  4. Clover/
  5. 2026-02-25.preview

Adds Smart Disputes settings to v2 AccountsPublic preview

What’s new

Adds the smart_disputes hash to the configuration.merchant field on the v2 Account object. The smart_disputes hash contains an auto_respond configuration that lets platforms control whether connected accounts automatically respond to disputes using Smart Disputes.

The auto_respond configuration includes two fields:

  • preference: A writable parameter that accepts on, off, or inherit values to control the Smart Disputes setting. When you set preference to inherit, the connected account uses your platform’s default Smart Disputes configuration.
  • value: A read-only property that shows the effective setting value as either on or off.

You can update these settings when you create or update an account.

Impact

You can now configure Smart Disputes behaviour for your connected accounts programmatically. Previously, connected accounts could only manage Smart Disputes settings through their Dashboard access.

This change gives you programmatic control over how disputes are handled for individual connected accounts while maintaining the flexibility to let accounts inherit your platform’s default configuration.

Changes

ParameterChangeResources or endpoints
smart_disputesAdded
V2.Core.Account#create.configuration.merchantV2.Core.Account#update.configuration.merchantV2.Core.Account.configuration.merchant

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: 2026-02-25.preview
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Chat with Stripe developers on Discord.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc
On this page