Dynamics 365 Commerce Omni-Channel Payments: Updates, Configuration, and What’s Next

August 26, 2021 Marcus Swift

Microsoft’s omni-channel payments for Dynamics 365 Commerce allows the creation of an order in one channel and fulfillment in another channel. For example, buying online and picking an order up in the store. Microsoft has provided two main releases related to omni-channel payments.

The original base release provided the features to take payments across the various channels as well as order workflows. In the summer of 2020, omni-channel Commerce order payments (OCCOP) was released adding a number of features to the original omni-channel payments release.

New Features in OCCOP

Among the features released in the OCCOP update:

  • Ability to enable editing of payments across channels and it now rationalizes the payments through the channels
  • Addition of a payment type field added to the sale order header
  • Default enabling of order completion for the call center channel
  • Ability to edit payments in the call center

It is worth noting that there are perquisites that must be enabled for the OCCOP to work, including:

  • Unified payment posting journal defaults for Commerce
  • Omni-channel payments
  • Duplicate payment protection on invoicing
  • Enable refunds over multiple captures
  • Enable manual void of expired credit card payment lines when authorizations are expired

Features Allowed for Payments

In addition to the capabilities mentioned above, some other key features rolled out for omni-channel payments in Dynamics 365 Commerce include the following:

  • Enable advanced external gift card
    • This feature supports the use of external gift cards within e-commerce and the call center channels.
    • SVS and Givex processers are supported out of the box with the Adyen connector.
  • Purchasing gift cards through the e-commerce channel
    • The gift cards are issued during invoicing in the back office.
  • Unified payment posting
    • Adds consistency in the journal naming for payments across the different order channels.
  • Skip “Change due” dialog in POS
    • Ability to disable the change due dialog that displays in the POS channel when no amount is due back to the customer.
  • Require card for POS orders
    • Prevents the pay later ability when and order is created through the POS channel.
  • Wallet payment support
    • Added to support the PayPal connector for payment methods where no BIN is provided and thus makes the BIN range not required to be setup.
    • The setup maps card IDs to payment connectors. Currently this only supports PayPal but additional connectors through Adyen are coming in the 10.0.19 update.
  • Archive credit card transaction data
    • Credit card transactional data is archived to the Azure blob storage to help keep the HQ database slim.
    • It’s important to consider how long you honor refunds before setting up how many days back to archive credit card transactions. Once the transaction is archived, refunds can’t be issued.
  • Process credit cards without a hardware station
    • Supports curbside pickup and the use of any cloud POS device for pickup of orders.

Key Bug Fixes

Bug fixes that have been introduced as part of the feature management releases include the following:

  • Duplicate payment protection on invoicing
  • Enabling the ability to manually void expired credit card payment lines when authorizations have expired
  • Enabling refunds over multiple payment captures
  • Enhanced handling of declined secondary payment authorizations

Out of Box Connectors


Adyen is an out of box supported payment connector for omni-channel payments. When used in POS, Adyen payment terminals are required. Currently the V002 version of the Adyen connector should be used as it adheres to authorization requirements from EU banks.

It is also important to note that when using the Adyen payment connector, do not enable the card verification values in the back office in AR parameters. There is also a setup for the authorization stale period in both the payment connector and in the AR parameters. The stale period in the payment connector needs to be set to occur after the stale period setup in the AR parameters.

One last tip to note: There is an optional domain field in the connector configuration. This is not actually optional but is required to go live.


PayPal is the other out-of-box connector supported by Microsoft. Two things to note for the PayPal connector:

  1. PayPal express and billing agreements are not currently supported by Microsoft.
  2. You cannot use the test PayPal connector in UAT or Prod environments. The test connector can only be used in Dev/Sandbox environments.

Upcoming Features

As of February 2021, the below upcoming features where planned:


  • Single payment authorization for orders that are fulfilled with multiple invoices.


  • Wallet payment method support through the Adyen connector.
  • Checkout refactoring for payments. Authorization will be done in a single request rather than two requests (1 for token and 1 for authorization).

In the pipeline, Google and Apple Pay will be supported through the Adyen connector.


If you’d like to learn more about omni-channel payment options and capabilities for your business, contact our experts at Western Computer.

About the Author

Marcus Swift

Marcus Swift is an experienced developer that has worked extensively with Dynamics AX and Dynamics 365 Finance.

More Content by Marcus Swift
Previous Video
How to Optimize Your Resource Scheduling In Dynamics 365 Field Service
How to Optimize Your Resource Scheduling In Dynamics 365 Field Service

Next Video
Dynamics 365 Business Central: Available to Promise vs Capable to Promise | Western Computer
Dynamics 365 Business Central: Available to Promise vs Capable to Promise | Western Computer

Learn more about Available to Promise and Capable to Promise in Microsoft Dynamics 365 Business Central. Co...