- Breaking changes
- Public preview
Renames the parameter for custom settlement timing on the Balance Settings API Breaking changes Public preview
What’s new
This change renames the top-level delay_days parameter of the Balance Settings API to delay_days_override to clearly distinguish between Stripe’s default settlement timing and whether your platform requests to override that computed delay.
Platforms can request a specific delay_days_override by creating or updating Balance Settings. Stripe uses the request to determine the final number of days to hold charge funds before they become available. If your platform doesn’t explicitly request a delay_days_override, we apply default settlement timing.
Why is this a breaking change?
We renamed the delay_days parameter to delay_days_override.
Impact
If you participate in the Accounts v2 API public preview and want to use API version 2025-07-30.preview or later, you need to update your integration to use the new parameter name.
If your integration relies on the ability to specify your own settlement timing with delay_days, update your Balance Settings integration to use the delay_days_override parameter.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| delay_days_override | Added | BalanceSettings#update. settlement_timing |
| delay_days | Removed | BalanceSettings#update. settlement_timing |
Upgrade
- View your current API version in Workbench.
- 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-07-30. preview
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.