Stripe v2 Accounts configure Smart Disputes auto-response
Introduced 2026-02-25 · score 0.91
HOW TO USE IT
When configuring a connected account’s Smart Disputes auto-response through the v2 Accounts API, set `configuration.merchant.smart_disputes.auto_respond.preference` to `on`, `off`, or `inherit`. Read `value` to see the effective setting.
curl -X POST https://api.stripe.com/v2/core/accounts/<ACCOUNT_ID> -H "Authorization: Bearer <SECRET_KEY>" -H "Stripe-Version: 2026-02-25.preview" --json '{"configuration":{"merchant":{"smart_disputes":{"auto_respond":{"preference":"inherit"}}}}}'curl -X POST https://api.stripe.com/v2/core/accounts -H "Authorization: Bearer <SECRET_KEY>" -H "Stripe-Version: 2026-02-25.preview" --json '{"configuration":{"merchant":{"smart_disputes":{"auto_respond":{"preference":"inherit"}}}}}'WHY THIS HELPS
When managing dispute response settings for connected accounts through the v2 Accounts API, configure each account’s Smart Disputes auto-response preference.
BEFORE THIS CHANGE
Connected accounts could manage Smart Disputes settings only through their Dashboard access.
REQUIREMENTS AND LIMITATIONS
- Availability: v2 Accounts API version 2026-02-25.preview
- id (required): Account ID to update.
- configuration: Account Configuration object; includes the merchant configuration.
- configuration.merchant.smart_disputes.auto_respond.preference: Writable preference. Allowed values: `on`, `off`, `inherit`; `inherit` uses the platform’s default Smart Disputes configuration. Values are alternatives; docs do not state they are mutually exclusive.
- configuration.merchant.smart_disputes.auto_respond.value: Read-only effective setting, shown as `on` or `off`.
- Stripe-Version (required): API version header; the official create/update examples use `2026-02-25.preview`.
- Authorization (required): Bearer secret key for the request.
- Prerequisite: Accounts v2 must be enabled for the platform; Stripe documents `accounts_v2_access_blocked` when it is not enabled.
- Prerequisite: Use API version `2026-02-25.preview` for the documented release-version request.
- `preference` is writable; `value` is read-only.
- When `preference` is `inherit`, the connected account uses the platform’s default Smart Disputes configuration.
FIRST-PARTY EVIDENCE
- https://docs.stripe.com/changelog/clover/2026-02-25/smart-disputes-v2-accounts
- https://docs.stripe.com/api/v2/core/accounts/update?api-version=2026-02-25.preview
- https://docs.stripe.com/api/v2/core/accounts/create?api-version=2026-02-25.preview
Check the installed version and the source before using it. Entry JSON