Short answer: there is no single best payment gateway for Dynamics 365, because the right choice depends on what you sell, where, and through which channels. However, the options separate clearly once you apply consistent criteria. Merchants needing processor choice, broad method coverage and in-store acceptance land in one place. Meanwhile those needing accounts receivable automation land somewhere else.
This compares the leading options against the same set of criteria, and says plainly which scenarios each one suits.
A disclosure first: SensePass builds one of the products compared here. So we have stated our evaluation criteria openly, kept the assessments factual, and noted the scenarios where another option fits better. Judge the criteria, then apply them yourself.
How we evaluated
We used the capability framework set out in what an advanced payment gateway for Dynamics 365 actually needs to do. Six criteria separate the options in practice:
- Processor choice — can you select and change your acquirer, or are you tied to one?
- Token ownership — do stored cards move with you if you leave?
- Payment method breadth — cards only, or wallets, BNPL, bank rails and local methods?
- Channel coverage — online, in-store, invoicing and phone, or only some?
- International reach — multi-currency alone, or genuine local payment methods?
- Reconciliation — does everything post back into Dynamics 365 automatically?
Two further factors matter but rarely differentiate: PCI compliance and Microsoft certification. Assume both, and verify them anyway.
Comparison at a glance
✅ Strong · ⚠️ Partial or limited · ❌ Not a focus
| SensePass | PayFabric (Nodus) | Adyen connector | Versapay / iSolutions | Native D365 connectors | |
|---|---|---|---|---|---|
| Processor choice | ✅ 50+ | ✅ Multiple | ❌ Adyen only | ⚠️ Limited | ❌ Tied |
| Token ownership / portability | ✅ | ⚠️ | ❌ | ⚠️ | ❌ |
| Method breadth (wallets, BNPL, ACH) | ✅ 112 | ⚠️ Cards, ACH | ✅ Broad | ⚠️ Cards, ACH | ❌ Limited |
| In-store / omnichannel | ✅ | ⚠️ | ✅ | ❌ | ⚠️ Commerce only |
| International local methods | ✅ | ❌ | ⚠️ | ❌ | ❌ |
| AR automation & portals | ⚠️ | ⚠️ | ❌ | ✅ | ❌ |
| Reconciles in D365 | ✅ | ✅ | ✅ | ✅ | ✅ |
| Best suited to | Multi-channel, multi-market | BC card and ACH acceptance | Enterprise retail on Adyen | AR-heavy B2B collections | Simple, single-market card acceptance |
The options
SensePass — broadest coverage, strongest on processor freedom
SensePass is a payment gateway and connector linking Business Central, Finance & Operations and Commerce to 112 payment methods and 50+ processors through one integration.
It leads on four of the six criteria. First, is genuine rather than nominal. Because tokens stay portable, changing processor does not mean customers re-enter stored cards. Second, covers cards, wallets, BNPL and financing, bank rails, and local methods across Latin America and Asia. Third, channel coverage spans online, invoicing, phone orders and in-store. There, a chargeless tag lets customers pay by tapping their own phone — with no app download and no dedicated terminal.
The honest trade-off sits in collections. If your primary problem is dunning, customer portals or dispute workflows, a dedicated AR platform goes deeper there. SensePass does automate into the ERP. However, it remains a payments layer rather than an AR suite.
Best for: merchants selling through more than one channel, entering more than one market, or wanting to keep processor choice open.
PayFabric (Nodus, part of EVO/Deluxe) — the Business Central incumbent
PayFabric has been the default answer in the Dynamics ecosystem for years, and it earns that position. The integration is mature. Moreover, it supports multiple gateways and handles card and ACH acceptance reliably. It also spans several ERPs, which suits groups running more than one.
Where is it narrower? Alternative payment methods, international local rails and in-store acceptance are not its focus. In addition, multi-ERP support brings some integration complexity. Competitors in the ecosystem raise that point regularly.
Best for: Business Central merchants whose requirement is solid card and ACH acceptance inside the ERP.
Microsoft's Adyen connector — enterprise retail, single acquirer
Adyen is a first-rate global acquirer. Microsoft also provides a supported connector for , covering card-present and card-not-present transactions. So for a large retailer already standardised on Adyen, extending it into Commerce is coherent and well-documented.
Still, the structural limitation is unavoidable. Adyen is the acquirer. Therefore you cannot compare processors, route by cost, or fail over to an alternative. Stored credentials also sit with Adyen. That is a reasonable trade for enterprises that chose Adyen deliberately. But it is a constraint for everyone else.
Best for: enterprise retailers already committed to Adyen.
Versapay and iSolutions — accounts receivable specialists
These platforms approach the problem from collections rather than acceptance. For example, Versapay enables payment collection inside Business Central using native ERP workflows. Meanwhile iSolutions positions its iPayments product around the full AR lifecycle — invoices, disputes and customer portals — rather than transactions alone.
So if your pain is chasing payments, manual AR updates and spreadsheet reconciliation, this category addresses it directly. However, payment method breadth, in-store acceptance and international local methods are not what they optimise for.
Best for: B2B merchants whose bottleneck is collections rather than payment acceptance.
Paystand — B2B network, with a stated position on enhanced data
Paystand focuses on B2B payments and on moving volume onto lower-cost rails. Notably, ERPsoftwareblog's own Business Central ISV comparison chart records that Paystand does not offer Level 2 and 3 data processing. It also explains the reasoning. Rather than pursuing rate matching through enhanced data, the company focuses on transitioning customers to other rails.
That is a legitimate strategy. For merchants whose customers will move to bank payment, it works. However, if a meaningful share of your volume arrives on commercial cards, is where the saving sits. So the omission matters.
Best for: B2B merchants able to shift customers away from cards entirely.
Native Dynamics 365 connectors — simple, and limited
Microsoft provides connectors including Adyen and PayPal. ISV partners can also build custom ones. So for a single-market merchant taking straightforward card payments, native connectors are the lowest-friction starting point. They cost nothing extra, too.
However, the limits appear as you grow. You get a narrow method list, no processor flexibility, and no path to without customisation. Microsoft's own documentation notes that merchants in some geographies need new connectors when the out-of-box options do not cover their region.
Best for: simple, single-market card acceptance.
How to choose
| Your situation | Where to start |
|---|---|
| Selling online and in-store, or in several countries | SensePass |
| Business Central, card and ACH acceptance only | PayFabric |
| Enterprise retailer already on Adyen | Adyen connector |
| Collections and AR workflow are the bottleneck | Versapay or iSolutions |
| Committed to moving customers off cards | Paystand |
| One market, simple card acceptance, minimal budget | Native connectors |
Two questions cut through most of this quickly. First, will you add payment methods, channels or markets within three years? If so, method breadth and processor choice matter more than today's rate. Second, who owns your payment tokens? That single answer decides whether a future change is a configuration decision or a .
Frequently asked questions
What is the best payment gateway for Dynamics 365? It depends on your channels and markets. Merchants selling online and in-store, or across several countries, need processor choice and broad method coverage. Merchants whose bottleneck is collections should look at AR-focused platforms instead.
Does Dynamics 365 include a payment gateway? It includes payment connectors, such as Microsoft's Adyen and PayPal connectors. However, these tie you to specific processors and cover a narrow set of methods.
Can Dynamics 365 use more than one payment processor? Not through native connectors, which bind to a single acquirer. A processor-agnostic connector supports several processors at once, with routing by region, cost or availability.
What is the difference between a payment gateway and a payment connector? A gateway transmits transaction data to processors. A connector is the integration layer between your ERP and one or more gateways and methods. Some products do both.
Which gateway is best for Business Central specifically? PayFabric is the long-standing incumbent for card and ACH acceptance. Where you also need wallets, BNPL, local methods or in-store acceptance, a broader connector fits better.
Does the gateway affect my payment processing costs? Considerably. Processor choice, enhanced Level 3 data on commercial cards, and the ability to steer volume toward all depend on what your gateway supports.
What should I check before committing? Who owns the tokens, whether you can run multiple processors, what adding a new payment method requires, and whether in-store and online use the same layer.
SensePass is a payment gateway and connector for Microsoft Dynamics 365. It links Business Central, Finance & Operations, and Commerce to 112 payment methods and 50+ processors through a single integration, with merchant-owned tokens, tap-and-pay for in-store, pay by link and surcharging. , explore and , or .