# Adds payment intent data configuration when updating Checkout Sessions ## What’s new You can now pass [payment_intent_data](https://docs.stripe.com/api/checkout/sessions/update.md?api-version=2026-10-28.endive#update_checkout_session-payment_intent_data) when you [update a Checkout Session](https://docs.stripe.com/api/checkout/sessions/update.md?api-version=2026-10-28.endive) that uses `mode=payment` and `ui_mode=elements`. This lets you configure selected PaymentIntent parameters after creating the Checkout Session and before confirming the payment. The supported sub-parameters are [description](https://docs.stripe.com/api/checkout/sessions/update.md?api-version=2026-10-28.endive#update_checkout_session-payment_intent_data-description), [metadata](https://docs.stripe.com/api/checkout/sessions/update.md?api-version=2026-10-28.endive#update_checkout_session-payment_intent_data-metadata), [setup_future_usage](https://docs.stripe.com/api/checkout/sessions/update.md?api-version=2026-10-28.endive#update_checkout_session-payment_intent_data-setup_future_usage), [statement_descriptor](https://docs.stripe.com/api/checkout/sessions/update.md?api-version=2026-10-28.endive#update_checkout_session-payment_intent_data-statement_descriptor), and [statement_descriptor_suffix](https://docs.stripe.com/api/checkout/sessions/update.md?api-version=2026-10-28.endive#update_checkout_session-payment_intent_data-statement_descriptor_suffix). These values are applied when the PaymentIntent is created at confirmation time and aren’t returned on the Checkout Session response. If you update `setup_future_usage`, you must wrap the Checkout Session update in `runServerUpdate` on the client side and await it before continuing with the payment. This keeps the payment method list and terms display synchronized. ## Impact You can defer PaymentIntent configuration to later in the checkout flow for [Checkout](https://docs.stripe.com/checkout/quickstart.md) integrations that use Elements. For example, you can update `setup_future_usage` after a customer chooses to save their payment method, or add order-specific `metadata` and `description` values after your server creates the final order. This parameter is only available for Checkout Sessions with `mode=payment` and `ui_mode=elements`, and can only be updated while the session is active. ## Changes #### REST API | Parameter | Change | Resources or endpoints | | --- | --- | --- | | `payment_intent_data` | Added | [Checkout.Session#update](/api/checkout/sessions/update?api-version=2026-10-28.endive#update_checkout_session) | #### Ruby | Parameter | Change | Resources or methods | | --- | --- | --- | | `payment_intent_data` | Added | [Checkout::SessionUpdateParams](/api/checkout/sessions/update?api-version=2026-10-28.endive#update_checkout_session) | #### Python | Parameter | Change | Resources or methods | | --- | --- | --- | | `payment_intent_data` | Added | [checkout.SessionModifyParams](/api/checkout/sessions/update?api-version=2026-10-28.endive#update_checkout_session) | #### PHP | Parameter | Change | Resources or methods | | --- | --- | --- | | `payment_intent_data` | Added | [Checkout\Session.update().$params](/api/checkout/sessions/update?api-version=2026-10-28.endive#update_checkout_session) | #### Java | Parameter | Change | Resources or methods | | --- | --- | --- | | `paymentIntentData` | Added | [checkout.SessionUpdateParams](/api/checkout/sessions/update?api-version=2026-10-28.endive#update_checkout_session) | #### Node.js | Parameter | Change | Resources or methods | | --- | --- | --- | | `payment_intent_data` | Added | [Checkout.SessionUpdateParams](/api/checkout/sessions/update?api-version=2026-10-28.endive#update_checkout_session) | #### Go | Parameter | Change | Resources or methods | | --- | --- | --- | | `PaymentIntentData` | Added | [CheckoutSessionParams](/api/checkout/sessions/update?api-version=2026-10-28.endive#update_checkout_session) | #### .NET | Parameter | Change | Resources or methods | | --- | --- | --- | | `PaymentIntentData` | Added | [Checkout.SessionUpdateOptions](/api/checkout/sessions/update?api-version=2026-10-28.endive#update_checkout_session) | ## Upgrade #### REST API 1. [View your current API version](https://docs.stripe.com/workbench/guides.md#view-api-versions) 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-versions.md#how-versions-are-specified-in-requests) to include `Stripe-Version: 2026-10-28.endive` 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). 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 Open USD (OUSD) as a supported token currency for crypto payments](https://docs.stripe.com/changelog/endive/2026-10-28/ousd-token-currency.md) - [Adds support for requesting Scalapay Payment Links](https://docs.stripe.com/changelog/endive/2026-10-28/scalapay-payment-method-support-payment-links.md) - [Adds the evidence submission method property to Disputes](https://docs.stripe.com/changelog/endive/2026-10-28/evidence-submission-method-property-disputes.md) - [Adds the ability to specify the intended submission method for Disputes](https://docs.stripe.com/changelog/endive/2026-10-28/adds-intended-submission-method-for-disputes.md) - [Adds invoice settings parameters for Checkout Sessions and Payment Links subscriptions](https://docs.stripe.com/changelog/endive/2026-10-28/invoice-settings-parameters-checkout-sessions-payment-links-subscriptions.md) - [Adds support for submitting evidence to appeal dispute decisions](https://docs.stripe.com/changelog/endive/2026-10-28/evidence-submission-appeal-dispute-decisions.md) - [Adds refund reference tracking for Klarna, PayPal, and Afterpay Clearpay](https://docs.stripe.com/changelog/endive/2026-10-28/refund-reference-klarna-paypal-afterpay.md) - [Adds support for specifying card-on-file usage when saving or charging cards](https://docs.stripe.com/changelog/endive/2026-10-28/card-on-file-usage-indicators-support.md) - [Adds RTP and FedNow as US bank transfer network types for cash balance transactions](https://docs.stripe.com/changelog/endive/2026-10-28/rtp-fednow-support-us-bank-transfer-network-types.md) - [Adds webhook events and error messages for the Standalone 3DS API](https://docs.stripe.com/changelog/endive/2026-10-28/standalone-3ds-error-messages-and-webhook-events.md)