Commerce payment packaging support in Service Fabric deployments

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Important

Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned

Enabled for	Public preview	General availability
End users, automatically	Mar 31, 2020	To be announced

Business value

This features allows payment packages to be deployed to on-premises environments. Previously, payment extension packages were only supported in cloud environments, blocking customers from using payment extensions in Dynamics 365 Commerce in on-premises environments.

Feature details

Extensions can be used to create new payment packages in Dynamics 365 Commerce, add the payment libraries as a reference to the extension model, and do customizations. All payment extension modules must begin with (or be prefixed with) the name RetailPaymentConnectors. If the model uses a different prefix, then it will not be considered to be a payment module. After the customization, you can create the deployable package and deploy it using Dynamics Lifecycle Services (LCS).

See also

Create payment packaging for Application Explorer in Service Fabric deployments (docs)