# Thin events now include field changes on related objects ## What’s new Thin events now include a before-and-after representation of what changed on the related object. The [changes](https://docs.stripe.com/api/v2/core/events/object.md?api-version=2025-11-17.preview#v2_event_object-changes) field contains two optional sub-fields: - `before`: The previous values of the fields that changed - `after`: The new values of the fields that changed Only modified fields are included in the `before` and `after` objects, allowing you to identify exactly what changed without needing to compare full object representations. In this release, the following event types support the `changes` field: - [v2.core.account.closed](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.core.account.closed) - [v2.core.account.created](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.core.account.created) - [v2.core.account.updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.core.account.updated) - [v2.core.account[configuration.customer].capability_status_updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.core.account%5Bconfiguration.customer%5D.capability_status_updated) - [v2.core.account[configuration.merchant].capability_status_updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.core.account%5Bconfiguration.merchant%5D.capability_status_updated) - [v2.core.account[configuration.recipient].capability_status_updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.core.account%5Bconfiguration.recipient%5D.capability_status_updated) - [v2.core.account[configuration.storer].capability_status_updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.core.account%5Bconfiguration.storer%5D.capability_status_updated) - [v2.core.account[defaults].updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.core.account%5Bdefaults%5D.updated) - [v2.money_management.outbound_payment.updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.money_management.outbound_payment.updated) - [v2.money_management.outbound_transfer.updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.money_management.outbound_transfer.updated) - [v2.money_management.payout_method.updated](https://docs.stripe.com/api/v2/core/events/event-types.md?api-version=2025-11-17.preview#v2_event_types-v2.money_management.payout_method.updated) ## Impact The `changes` field simplifies webhook processing by providing an immediate view of what changed on an object. Instead of storing previous object states or comparing full objects to identify changes, you can now directly inspect the `before` and `after` values. This is particularly useful for: - Building audit logs that track specific field changes - Triggering conditional logic based on which fields were modified - Debugging webhook events by quickly understanding what triggered the event ## Changes #### REST API | Parameter | Change | Resources or endpoints | | --------- | ------ | -------------------------------------------------------------------------- | | `changes` | Added | [V2.Core.Event](/api/v2/core/events/object?api-version=2025-11-17.preview) | #### Ruby | Parameter | Change | Resources or methods | | --------- | ------ | ---------------------------------------------------------------------------- | | `changes` | Added | [V2::Core::Event](/api/v2/core/events/object?api-version=2025-11-17.preview) | #### Python | Parameter | Change | Resources or methods | | --------- | ------ | -------------------------------------------------------------------------- | | `changes` | Added | [V2.Core.Event](/api/v2/core/events/object?api-version=2025-11-17.preview) | #### PHP | Parameter | Change | Resources or methods | | --------- | ------ | -------------------------------------------------------------------------- | | `changes` | Added | [V2.Core.Event](/api/v2/core/events/object?api-version=2025-11-17.preview) | #### Java | Parameter | Change | Resources or methods | | --------- | ------ | -------------------------------------------------------------------------- | | `changes` | Added | [v2.core.Event](/api/v2/core/events/object?api-version=2025-11-17.preview) | #### Node.js | Parameter | Change | Resources or methods | | --------- | ------ | -------------------------------------------------------------------------- | | `changes` | Added | [V2.Core.Event](/api/v2/core/events/object?api-version=2025-11-17.preview) | #### Go | Parameter | Change | Resources or methods | | --------- | ------ | ------------------------------------------------------------------------ | | `Changes` | Added | [V2CoreEvent](/api/v2/core/events/object?api-version=2025-11-17.preview) | #### .NET | Parameter | Change | Resources or methods | | --------- | ------ | -------------------------------------------------------------------------- | | `Changes` | Added | [V2.Core.Event](/api/v2/core/events/object?api-version=2025-11-17.preview) | ## 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. 1. 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: 2025-11-17.preview` 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. 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. 1. Upgrade your Ruby SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. 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. 1. Upgrade your Python SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. 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. 1. Upgrade your PHP SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. 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. 1. Upgrade your Java SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. 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. 1. Upgrade your Node SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. 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. 1. Upgrade your Go SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. 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. 1. Upgrade your .NET SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. 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).