What Microsoft has announced
The entry is listed as roadmap ID 577896 and is marked In development. It targets Dynamics 365 Commerce on the web, in the Worldwide (Standard Multi-Tenant) cloud. The planned dates are:
- Preview: January 2027
- General availability: June 2027
Microsoft's roadmap page says it gives estimated release dates and descriptions, and that all information is subject to change. Treat both dates as targets. Neither preview nor GA has begun as of today, November 17, 2026.
What the service is meant to do
Per the roadmap description, the service gives organisations one shared payment layer on Microsoft Dataverse. They can plug it into their Dynamics 365 business workflows. The named scenarios are collecting payments for:
- invoices
- sales orders
- work orders
Applications would call a common set of payment APIs for four operations: authorize, capture, void and refund. These run through cloud-connected payment terminals.
How it is configured
Administrators pick a payment connector and set its merchant settings in connector profiles. Adyen support is built in. Partners can add other connectors through extension solutions. Microsoft says this needs no change to the core service and no new payment APIs.
Each customer's service and payment configuration lives in that customer's own Dataverse environment.
What isn't specified
The roadmap entry leaves several things open:
- Supported applications. It says "supported applications" without naming them. Don't assume every Dynamics 365 app is included.
- Terminals. It gives no hardware list, no offline behaviour and no per-region availability. It says only "cloud-connected".
- Providers. Adyen is built in, but the entry doesn't say whether it is the only provider at launch. It also doesn't say how customers contract with Adyen.
- Data handling. The Dataverse-environment statement describes where configuration lives. It doesn't tell you how credentials are protected, how long transaction records are kept, or how compliance and residency work.
- Existing setups. It doesn't say whether this replaces or sits alongside current Commerce payment setups.
How it compares with today's Commerce payments
Commerce already has a mature payment story. The online checkout payment module interacts with the Commerce Scale Unit to retrieve the Adyen payment information. It also supports strong customer authentication (SCA).
The current Adyen connector setup has its own prerequisites and version limits:
- You need a separate agreement with Adyen.
- Connector version V001 is no longer supported for call center and Commerce e-commerce, because it relied on Adyen-hosted payment pages.
- Microsoft's setup guide recommends V003 for new implementations. V003 is available in Commerce 10.0.29 and later.
- Terminal setup today runs through POS hardware profiles. Local-network or cloud architectures are configured through an EFT service. Terminals need an IP address or POIID.
Microsoft's Learn documentation also shows that Dataverse already plays a part in Commerce payments. Pay by link is the example: to receive payment notifications, you must link your Commerce environment to a corresponding Dataverse environment. A Dataverse-hosted payment service is therefore consistent with where Commerce payments are already heading.
I wouldn't carry any of today's connector versions or setup steps over to the new service. Microsoft hasn't published implementation guidance for it.
Why it could matter
This part is my analysis, not something Microsoft has confirmed. A common API with connector profiles could mean each business app doesn't have to build its own payment handling. The partner extension model could also widen provider coverage beyond Adyen. Taking payments on a work order or invoice is a different problem from running a retail checkout. A shared service looks aimed at that gap.
The risks are the usual ones for a new payments layer. These include compatibility with existing connectors, the migration path, licensing, and who is responsible for PCI and compliance. None of that is answered yet.
What admins and partners should do now
- Put January 2027 preview and June 2027 GA on the watch list, and expect them to move.
- Inventory where you take payments today: POS, call center, e-commerce, and invoices or work orders handled outside Commerce.
- Check your Dataverse environment strategy. The service is described as living per customer environment, so your environment layout matters.
- If you use Adyen, keep your existing connector current. Confirm you aren't on V001, and plan for V003.
- Partners building payment integrations should wait for Microsoft's extension-solution documentation. Don't build against assumptions.
- When preview documentation appears, check the supported apps, terminal compatibility, security model, licensing and coexistence guidance first.
Bottom line
This is a credible roadmap item with a clear architectural direction: one payment service on Dataverse, common APIs, and pluggable connectors. For now, the substance is the plan and the schedule. Concrete answers on applications, terminals, security and migration should come with the preview.
References
- Dynamics 365 Commerce: Payments-as-a-Service for Dynamics 365 Microsoft 365 Roadmap · 2026-11-17T19:37:19.490977Z
- Set up Dynamics 365 Payment Connector for Adyen - Commerce | Dynamics 365 | Microsoft Learn learn.microsoft.com
- Microsoft Copilot Roadmap | Microsoft 365 microsoft.com