Patrick Mouwen Patrick Mouwen PMN Consulting
Release Analysis & Technical Resources · 17 September 2025

Commerce CSU V9.55/10.0.45 - September 2025

For anyone new in this field: D365 Commerce CSU is shipped as part of D365 ERP. It comes with 650 APIs out of the box which enables the use of ERP and CRM data and business logic in B2C and B2B commerce.

I have been using Commerce CSU for integration scenarios since its early days around 2015. I am sharing my knowledge to enable anyone to use Commerce CSU effectively for their B2C and B2B Commerce applications (e-commerce, POS, Customer Service etc.)

In that context, I am publishing these unofficial D365 Commerce CSU Release Notes with any upcoming new Dynamics 365 ERP and Commerce platform Release.

A-Release Note Details

These release notes are applicable to the following CSU and D365 ERP version:

This new version (9.55.25240.5 / 10.0.45) doubles down on payments and checkout hardening— Changes pivot around five themes:

  • External/third-party gift cards after payment: new line-level fields on (e.g., approval and tender type) show up across /Carts, /SalesOrders, and related reads—enabling the “issue/fund only after payment succeeds” design that’s critical for SCO and fraud control.
  • Guest checkout control via API: /Carts/GetConfiguration now reflects the Allow anonymous checkout switch, aligning headless flows with your Online Functionality Profile.
  • Payment notification clarity: /PaymentNotifications surfaces a normalized processing status, making webhook-driven flows (including Pay by link) easier to reconcile and automate.
  • Refund usability: expanded EmployeePermissions support showing all refund methods (when policy allows), reducing manager overrides in return flows.
  • Azure Maps at channel level: /OrgUnits/GetOrgUnitConfiguration adds flags/keys so Store Locator, address suggest, and POS scenarios can move off Bing Maps (discontinued) cleanly.

Pay by link: if you’re using the out-of-box Adyen connector, these API updates complement that journey: notifications carry clearer status for Dataverse-backed processing, checkout settings are enforced consistently across headless vs. storefront, and post-payment gift-card issuance avoids value creation before funds clear.

B-Downloads for your convenience

  • Latest V9.55 CSU full interface specification in OpenAPI/Swagger format: Link
  • Lestest V9.55 Overview of required Commerce Roles for all nearly 800 APIs: Link

C-API and Schema Changes compared to the previous version 9.54/V10.0.44

C.1 New APIs

None

C.2 Removed APIs

None

C.3 Data Model Changes

1) External gift cards: new flags on line-level ThirdPartyGiftCardInfo

What changed (multiple APIs): gained and in cart/sales-line schemas. Likely intent: enable the “fund gift cards after payment is completed” design and surface the card’s tender type + approval state through the API (important for POS/SCO flows and fraud/risk controls).

2) Guest checkout hardening: CartConfiguration.AllowAnonymousCheckout

What changed: adds (returned by ). Likely intent: close the loophole where guest checkout could be invoked via APIs even if the storefront didn’t show it—making the API honor the Online Functionality Profile setting.

3) Refund policy usability: EmployeePermissions.AllowAllRefundPaymMethods

What changed: adds across Employees endpoints (, , and ). Likely intent: if a channel return policy hides certain payment methods and “Manager override” is on, authorized non-managers can still “Show all refund options” and finish the return—removing the manager dependency. This landed with 10.0.44 but is now reflected in the API surface.

4) Payment notifications: ProcessingStatusValue

What changed: adds to the entity and query shapes; / enums extended to include it; CRUD and updated accordingly. Likely intent: expose a normalized processing status on payment notifications for sorting/filtering and operational reconciliation (e.g., async gateway callbacks or retries).

5) Azure Maps enablement at channel level: ChannelConfiguration.AzureMapsEnabled/AzureMapsApiKey

What changed: extends with and . Likely intent: support Bing Maps retirement by allowing Azure Maps for Store Locator, BOPIS, address autosuggest, etc., and for POS scenarios.

C.4 New flight keys

Microsoft implements new CSU flight keys with every new CSU version. These undocumented flight keys steer specific CSU behavior. Here is a list of the latest keys for V9.55/V10.0.45.

Based on our analysis of the code, the flight keys appear to be used as follows:

Disclaimer

The content of this article represents my independent technical analysis and personal interpretation of publicly available software artefacts. It is not endorsed by, affiliated with, or authorised by Microsoft Corporation. Nothing in this article constitutes official Microsoft documentation, guidance, or product commitments.

All findings are derived from analysis of the software and public documentation. Feature descriptions, presumable use cases, and “likely intent” assessments reflect my professional opinion based on observable code and API changes — they may not reflect Microsoft’s actual design intent, planned behaviour, or final implementation.

Information regarding features described as preview, private preview, or roadmap items is subject to change at Microsoft’s sole discretion and should not be relied upon for planning, purchasing, or architectural decisions. This article describes the product as at the date of publication above.

This article is provided for informational and educational purposes only, on an “as-is” basis without warranties of any kind, express or implied. The author assumes no liability for any direct, indirect, incidental, or consequential damages arising from the use of or reliance on the information contained herein.

For authoritative product information, consult Microsoft’s official documentation at learn.microsoft.com.

← All writing