# Adds the ability to reverse platform rejections on connected accounts

## What’s new

Adds the ability for your platform to reverse your own rejections on connected accounts using the new [Unreject an account](https://docs.stripe.com/api/account/unreject.md?api-version=2026-07-29.dahlia) endpoint.

Previously, reversing a rejection required you to contact Stripe support. The unreject action re-enables charges and payouts that were disabled by the rejection and reverts the account’s application state. You can only reverse rejections that your platform initiated. You can’t reverse Stripe-initiated rejections through this endpoint.

## Impact

If your platform incorrectly rejects a connected account or wants to re-enable an account after the merchant remediates an issue, you can self-serve immediately instead of waiting for Stripe support.

This reduces downtime for your connected accounts and helps you resolve false positives faster in your fraud review workflows.

## Changes

#### REST API

| Endpoint | Change | Resource |
| --- | --- | --- |
| `unreject` | Added | [Account](/api/accounts/object?api-version=2026-07-29.dahlia#account_object) |

#### Ruby

| Method | Change | Resource |
| --- | --- | --- |
| `unreject` | Added | [Account](/api/accounts/object?api-version=2026-07-29.dahlia#account_object) |

#### Python

| Method | Change | Resource |
| --- | --- | --- |
| `unreject` | Added | [Account](/api/accounts/object?api-version=2026-07-29.dahlia#account_object) |

#### PHP

| Method | Change | Resource |
| --- | --- | --- |
| `unreject` | Added | [Account](/api/accounts/object?api-version=2026-07-29.dahlia#account_object) |

#### Java

| Method | Change | Resource |
| --- | --- | --- |
| `unreject` | Added | [Account](/api/accounts/object?api-version=2026-07-29.dahlia#account_object) |

#### Node.js

| Method | Change | Resource |
| --- | --- | --- |
| `unreject` | Added | [Account](/api/accounts/object?api-version=2026-07-29.dahlia#account_object) |

#### Go

| Method | Change | Resource |
| --- | --- | --- |
| `Unreject` | Added | [Account](/api/accounts/object?api-version=2026-07-29.dahlia#account_object) |

#### .NET

| Method | Change | Resource |
| --- | --- | --- |
| `Unreject` | Added | [Account](/api/accounts/object?api-version=2026-07-29.dahlia#account_object) |

## Upgrade

#### REST API

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) 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](https://docs.stripe.com/api/versioning.md) to include `Stripe-Version: 2026-07-29.dahlia`
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Ruby

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Ruby SDK to the latest version.
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Python

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Python SDK to the latest version.
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### PHP

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your PHP SDK to the latest version.
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Java

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Java SDK to the latest version.
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Node.js

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Node SDK to the latest version.
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Go

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Go SDK to the latest version.
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### .NET

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your .NET SDK to the latest version.
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

## Related changes

- [Adds the ability to show who initiated a top-up](https://docs.stripe.com/changelog/dahlia/2026-07-29/top-up-initiated-by-property.md)
- [Adds Payment Method support to Top-ups](https://docs.stripe.com/changelog/dahlia/2026-07-29/adds-payment-method-support-to-top-ups.md)
- [Adds new address fields to Accounts v1 for Singapore compliance](https://docs.stripe.com/changelog/dahlia/2026-07-29/accounts-v1-address-fields.md)
- [Adds a new Smart Disputes management feature to Account Session embedded components](https://docs.stripe.com/changelog/dahlia/2026-07-29/account-session-embedded-components-smart-disputes-management.md)
- [Adds new address fields to Accounts v2 for Singapore compliance](https://docs.stripe.com/changelog/dahlia/2026-07-29/accounts-v2-address-fields.md)
- [Enables rejecting connected accounts with non-zero balances and controlling whether to pause payouts](https://docs.stripe.com/changelog/dahlia/2026-07-29/reject-connected-accounts-with-non-zero-balances.md)