Patrick Mouwen Patrick Mouwen PMN Consulting
Release Analysis & Technical Resources · 26 June 2025

Commerce CSU V9.54/10.0.44 - June 2025

For anyone new in this field: D365 Commerce CSU is shipped as part of D365 ERP and comes with 650 APIs out of the box for use 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 integration scenarios (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 versions:

This CSU API release seems to focus on the latest Pay by link feature, which is availablefor the out-of-box Adyen payment connector. See more details here on Microsoft learn.

The Pay by link feature is based on the following components:

  • Payment notification service which is triggered from an Adyen webhook, sent to a Dataverse endpoint
  • The Dataverse endpoint is set up in the Commerce shared parameters
  • Features “Payment notifications”, “Pay by link payment”, “Enhanced wallet support” and “Payment improvements” to be enabled in D365 ERP
  • APIs which handle Payment notifications and Payment link
  • Pay by link button in the POS

B-Downloads for your convenience

  • Latest V9.54 CSU full interface specification in OpenAPI/Swagger format: Link

  • Lestest V9.54 Overview of required Commerce Roles for all nearly 800 APIs: Link

C-API and Schema Changes compared to the previous version 9.53/V10.0.43

C.1 New APIs

Related to Payment notifications:

For creating and maintaining a payment link:

C.2 Removed APIs

None

C.3 Data Model Changes

  • New property AsynchronousPayments on API requests and responses which work against Carts and SalesOrders
  • New property LoyaltyGroup]/LoyaltyProgramNextTierStatus on POST /Commerce/GetCustomerLoyaltyCards, /Commerce/ScanResults APIs and POST /Commerce/GetLoyaltyCard
  • New property IsUnifiedPaymentExperienceDisabled on GET /Commerce/GetDeviceConfiguration()
  • New property CardInteractionConfigurations on GET /Commerce/GetTenderTypes()

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:

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