October 2025 release

  • Updated

Release: 5.2.2510.958+sts

The following is a list of the release's bug fixes and enhancements. Some bug fixes may address existing support articles. A comprehensive list is at the bottom of this page.

The October 2025 release is now available for developers to download and work with locally or to request deployments.

Release highlights

  • Payment Service: Google Pay – You can now use Google Pay with Payment Service. See Enable Google Pay for Payment Service to get started. 
    • This feature is currently available on the multi-page checkout flow. Google Pay will be added to one-page checkout in a future release.
  • Import ODP audiences – You can sync standard audiences from Optimizely Data Platform (ODP) into Configured Commerce when you have the integration. See  Import ODP audiences into Configured Commerce for information.

Breaking changes

None.

API updates

  • Introduced the GET /api/v1/dealers/getByPath endpoint to retrieve dealer information by specifying its URL path.
  • Introduced the GET /api/v1/googlepay/config endpoint to retrieve the Google Pay configuration settings.
  • Updated the GET /api/v1/vmiLocations/{vmiLocationId}/bins endpoint with an optional query parameter, parameter.isBelowMaximum, to filter VMI (Vendor-Managed Inventory) bins that are below their maximum quantity.
  • Updated Carts and Checkout:
    • GET /api/v1/settings/cart now includes an enableGooglePay property in its response to indicate if Google Pay is enabled.
    • Insite.Cart.WebApi.V1.ApiModels.CartModel now contains a boolean property, enableGooglePay, to reflect the Google Pay setting. This update affects all endpoints that return the cart model, including quotes, jobquotes, and orderapprovals.
  • Updated Insite.Dealers.WebApi.V1.ApiModels.DealerModel to include detailPagePath and alternateLanguageUrls properties.

Enhancements

Spire

  • Added multi-language support for image badges.

Other

  • Added the ability to use Google Pay with Payment Service.
  • Added a Personas Import API Key setting to export personas from Optimizely Data Platform (ODP). See Import ODP audiences into Configured Commerce for information.
  • Added retry logic to PDF generation to handle transient gRPC connection failures.
  • Updated the security validation logic for SecureEnableQueryAttribute to prevent unauthorized filtering on hidden properties within navigation entities. This protects sensitive data by properly validating hidden properties when accessed through navigation paths. Additionally, null safety in the ThrowResponseException method has been improved for .NET 6+ environments.
  • Suppressed error messages for invalid admin URLs.

Bug fixes

  • Fixed an issue where saved credit cards were tokenized for every transaction in Spreedly, rather than new credit cards only.
  • *Fixed an issue where OrderLineVat and OrderLineRfq showed custom properties for non-related entities.
  • *Fixed an issue where the URL duplicated the language segment when you switched languages on the Brands page.
  • *Fixed an issue where abandoned emails for products with long names reached the limit of the database subject field.
  • *Fixed a transitive dependency on Portable.BouncyCastle when upgrading.
  • *Fixed an issue where require statements in some blueprints were incompatible with the Webpack plugin and generated an async widget definition file.

* These bug fixes were included in hotfixes and are available for 5.2.2509 STS.

Related Support Articles

None.

Configured Commerce REST APIs