Enables rejecting connected accounts with non-zero balances and controlling whether to pause payouts
What’s new
Adds the ability to reject a connected account even when it has a non-zero balance. You can also control if payouts are paused as part of the rejection by passing the new payouts_action parameter, which accepts pause (default) or none.
Previously, attempting to reject an account with a non-zero balance using the Reject an account endpoint returned an error, and payouts were always paused during rejection.
Impact
If your integration rejects connected accounts using the Reject an account endpoint, you can now reject accounts regardless of their balance. You can also use the new payouts_action parameter to keep payouts enabled after rejection by passing none.
This gives you the flexibility to reject connected accounts without having to first remediate any negative or positive balances.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| payouts_action | Added | Account#reject |
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: 2026-07-29. dahlia
- 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.
Related changes
- Adds the ability to show who initiated a top-up
- Adds Payment Method support to Top-ups
- Adds new address fields to Accounts v1 for Singapore compliance
- Adds a new Smart Disputes management feature to Account Session embedded components
- Adds new address fields to Accounts v2 for Singapore compliance
- Adds the ability to reverse platform rejections on connected accounts