We’ve spent more than 33 years building payment connectors for Microsoft Dynamics, and in that time one question has come up more than any other: “Can we accept PayPal in Dynamics 365?” And right behind it: What about Venmo? Klarna? Apple Pay and Google Pay? Affirm or Afterpay? ACH and pay-by-bank? Amazon Pay? Even crypto?
The names on that list change with the decade — it used to be gift cards, then wallets, and today it’s BNPL and pay-by-bank. The underlying problem never changes. A customer wants to pay a certain way, the business wants to let them, and the native Dynamics 365 payment setup says no.
Here’s the short answer: yes, you can accept PayPal, Venmo, Klarna, and 100+ other payment methods in Dynamics 365 — but not through the native connector alone. You need a payment connector layer that sits between Dynamics 365 and the payments ecosystem. This article explains why the native path falls short, how the connector approach works, and what it takes to add these methods across Commerce, Finance & Operations, and Business Central.
Why native Dynamics 365 payment connectors limit your options
Microsoft Dynamics 365 is exceptional at running a business. It was never designed to be a payments platform, and its native payment connectors reflect that. Three limitations show up on nearly every implementation we work on:
You’re tied to a single acquirer. Most native connectors bind you to one acquiring bank. If that processor raises rates, underperforms on approvals, or has an outage, you have no alternative path — and switching means a re-integration project.
The method list is narrow. Native connectors are built around card present and card not present transactions. The wallets, BNPL providers, and bank rails your customers increasingly expect simply aren’t there.
Adding a method means custom development. Want PayPal on your eCommerce checkout and Klarna at your Store Commerce POS? Traditionally that’s two separate integration projects, each with its own certification, testing, and ongoing maintenance burden — and another one every time a new method becomes popular.
For a business trying to reduce cart abandonment or close bigger tickets, that’s a real revenue problem, not just a technical annoyance.
The fix: a payment connector layer
The modern approach is to stop integrating payment methods one at a time. Instead, you connect Dynamics 365 once to a payment connector that already maintains connections to the entire ecosystem — the methods, the processors, and the certifications.
This is the model behind PayFusion365 and our integration with SensePass. Dynamics 365 talks to the connector; the connector talks to everything else. When a new payment method gains traction, it’s added at the connector layer — you switch it on rather than commissioning a project.
Three practical consequences matter most:
- One integration, many methods. Enable PayPal, Venmo, Klarna, Apple Pay, ACH and more without a separate build for each.
- Processor freedom. Because the connector isn’t tied to a single acquirer, you can compare rates and switch processors without rebuilding — and without losing your stored payment tokens.
- Everything still reconciles in Dynamics 365. Transactions post back into your ERP automatically, so finance keeps a single source of truth.
What you can actually accept
Here’s the practical answer to “can we take X in Dynamics 365?” once a connector layer is in place:
| Category | Methods |
|---|---|
| Cards | Visa, Mastercard, American Express, Discover |
| Digital wallets | PayPal, Venmo, Apple Pay, Google Pay, Amazon Pay, Alipay, WeChat Pay |
| BNPL & financing | Klarna, Affirm, Afterpay, Sezzle, Zip, Splitit |
| Bank & open banking | ACH, pay-by-bank, SEPA, and local rails such as PIX (Brazil) and UPI (India) |
| Crypto | Bitcoin, Ethereum and other major currencies via supported providers |
| Payment links | Secure pay-by-link for invoices, phone orders, and remote sales |
That’s more than 100 methods in total, through 50+ card processors. For the full catalog, see the SensePass digital wallets and credit card processors pages.
How this works across each Dynamics 365 module
Dynamics 365 isn’t one product, and the payment story differs by module. Our joint integration covers all three of the modules where payments matter most.
Dynamics 365 Commerce (and Store Commerce POS)
Retail is where payment choice converts most directly into revenue. With a connector layer, the same set of methods is available online and at the point of sale — a shopper can use Apple Pay in your store and Klarna on your website, with both reconciling into the same system. This is also where omnichannel scenarios like buy-online-pickup-in-store and cross-channel returns need consistent payment handling. See Dynamics 365 Commerce payments for the retail and POS detail.
Dynamics 365 Finance & Operations
For enterprise finance teams, the wins are in receivables and reach. Embed a payment link directly in an AR invoice and the customer pays instantly by their preferred method, with the payment reconciled against the open invoice automatically. Add multi-currency support and local methods per region, and a global operation can collect everywhere without a separate integration per country. More on Dynamics 365 Finance & Operations payments.
Dynamics 365 Business Central
Smaller and mid-sized organizations feel the friction of manual AR most acutely. Adding payment links to Business Central invoices — and giving customers wallet, BNPL, and ACH options — shortens the collection cycle without adding headcount or requiring a developer. More on Business Central payments.
The business case: why method breadth pays for itself
Adding payment methods isn’t a checkbox exercise. In our experience across Dynamics implementations, three effects show up consistently:
Fewer abandoned checkouts. When a customer’s preferred method isn’t offered, a meaningful share simply leave. Wallets in particular remove friction because the payment credentials already exist on the device.
Larger average orders. BNPL and financing options change what a customer is willing to buy in a single transaction, which matters most for high-ticket goods and B2B orders.
Lower cost of acceptance. Two levers here. Processor flexibility lets you shop for better rates rather than accepting whatever your native connector is tied to. And steering customers toward low-cost rails like ACH or pay-by-bank meaningfully reduces fees on large invoices.
What to look for in a Dynamics 365 payment connector
If you’re evaluating options, these are the questions we’d tell any Dynamics customer to ask:
- Which modules does it actually support? Commerce, F&O, and Business Central are different integrations. Confirm the ones you run.
- Is it processor-agnostic? If it locks you to one acquirer, you’ve traded one constraint for another.
- Do you own your payment tokens? Token portability is what makes switching processors possible without re-collecting customer payment details.
- Does it cover in-person as well as online? If in-store requires a separate system, you don’t have unified commerce.
- How does reconciliation work? Payments should post back into Dynamics 365 automatically, not arrive as a file to import.
- What does adding a new method require? The answer should be “enable it,” not “scope a project.”
- Who supports it? Payments break at inconvenient moments. Know whether you’re calling a partner who understands Dynamics or a support queue that doesn’t.
Frequently asked questions
Can Dynamics 365 accept PayPal?
Yes. PayPal isn’t available through most native Dynamics 365 payment connectors, but it can be enabled through a payment connector layer such as PayFusion365 with SensePass, across Commerce, Finance & Operations, and Business Central.
How do I add Klarna or other BNPL options to Dynamics 365?
BNPL providers including Klarna, Affirm, Afterpay, Sezzle, and Zip are enabled at the connector layer rather than integrated individually. Once the connector is in place, you switch them on and they appear at checkout.
Can I accept Venmo in Dynamics 365?
Yes, through the same connector approach that enables PayPal — Venmo is supported alongside other digital wallets.
Do I need a developer to add new payment methods?
No. That’s the central advantage of the connector model: methods are added at the connector layer, so enabling a new one doesn’t require custom development or a new certification in your Dynamics 365 environment.
Can I switch payment processors without losing saved cards?
Yes, if your connector supports token portability. Because the tokens belong to you rather than the processor, you can migrate to a new processor without re-collecting customer payment details.
Does this work for in-store payments too?
Yes. With Dynamics 365 Commerce and Store Commerce POS, the same methods are available in person and online, with transactions reconciling into the same system.
Which Dynamics 365 versions are supported?
Our joint integration covers Dynamics 365 Commerce, Finance & Operations, and Business Central. Confirm your specific configuration during scoping.
Getting started
If your Dynamics 365 environment is limiting which payment methods you can offer, the fix is more accessible than most teams assume. The connector approach means one integration, then a settings change each time you want to add a method — rather than a development project.
Start by listing the methods your customers ask for and can’t currently use, then look at where those requests are costing you: abandoned carts, smaller orders, slow-paying invoices. That list usually makes the business case on its own.
For the full picture of what’s possible, see the SensePass Dynamics 365 payments overview — or get in touch with our team at New West Technologies to talk through your specific Dynamics configuration.
New West Technologies has been building payment connectors for Microsoft Dynamics for over 33 years. PayFusion365 integrates leading processors and payment methods with Dynamics 365 Commerce, Finance & Operations, Finance & Supply Chain, Business Central, and eCommerce. Learn more about PayFusion365 for SensePass.
Related: New West Unveils PayFusion365 for Sensepass (SensePay) for Business Central
