Short answer: Zip, Sezzle and Splitit can all be added to Dynamics 365 through a single payment connector — no separate integration per provider. Each one reaches a shopper the big three don’t, and because they run through the same connection, offering all of them costs roughly what offering one does. In-store, tap-and-pay means the customer pays without downloading any provider’s app.

Most BNPL articles stop at Klarna, Affirm and Afterpay. That’s a mistake, because the value of the next three isn’t volume — it’s coverage.

Why a fourth, fifth and sixth provider is worth having

BNPL adoption is account-driven. A shopper who already has a Sezzle account with a payment history isn’t going to apply for Klarna at your register — they’ll pay another way or abandon the purchase. Every provider you don’t offer is a segment of customers defaulting to a card, or to nothing.

With direct integrations, that logic collapses under its own weight: each additional provider is another API, another certification, another settlement format, another reconciliation process. Nobody builds six. With a connector, they’re already built — so coverage stops being a cost decision.

What each one actually adds

Zip is pay-in-four with wide merchant reach and a strong presence among shoppers who use it as a general-purpose installment option rather than a store-specific one. It’s a straightforward addition to a retail mix — a familiar name that catches customers already inside its ecosystem.

Sezzle skews younger and leans into credit-building features, appealing to shoppers deliberately avoiding traditional credit. For retailers selling to a Gen Z or young-millennial base, Sezzle reaches customers who may not have — or want — a credit card at all.

Splitit is the genuinely different one, and it’s underrated. Rather than issuing new credit, Splitit lets a customer split a purchase across their existing credit card — no application, no new credit line, no additional approval. That makes it a distinct proposition for higher-ticket purchases and for customers who don’t want another lending relationship. In a B2B or considered-purchase context, it’s often an easier “yes” than a new financing application.

Alongside these, WeGetFinancing extends the range further into longer-term financing for big-ticket retail.

Adding them to Dynamics 365

Dynamics 365 doesn’t support any of them natively — its payment connectors are built around cards, usually tied to a single acquirer. SensePass connects your existing environment to 100+ payment methods and 50+ processors through one integration, with Zip, Sezzle and Splitit already included.

One integration, all providers. Adding a provider is a configuration change. There’s no per-provider build, no separate certification cycle, and no change inside Business Central, Finance & Operations, or Commerce.

In-store without app downloads. This is where multi-provider support usually breaks down. Each BNPL provider’s native in-store path pushes the customer into that provider’s app to activate a virtual or wallet card — so supporting six providers in-store natively would mean six different counter experiences your staff must know. With tap-and-pay, there’s one: the customer taps their phone on a chargeless tag and picks their provider. No apps, no virtual cards, no terminal.

Everywhere else too. The same providers appear in your online checkout and in payment links for phone, quote, and remote sales.

The strategic point

Offering one BNPL provider is a feature. Offering the shopper’s own provider is a conversion strategy — and that only works if adding providers is close to free. That’s the structural advantage of the connector model, and the reason the “which BNPL provider should we pick?” question is usually the wrong one.

Pair these with Klarna, Affirm and Afterpay and you cover the overwhelming majority of BNPL-inclined shoppers in your market.

Reconciling multiple providers

Six providers means six settlement cycles, six fee structures, six refund behaviors. Done manually, that’s where finance teams drown. Done properly — clearing accounts per provider, settlement batch matching, automated fee and clawback journals — it’s routine. See BNPL reconciliation in Dynamics 365 for the architecture, and ERP accounts receivable for the broader collections picture.

Frequently asked questions

Can I add Zip, Sezzle and Splitit to Dynamics 365? Yes — all three are available through the SensePass connector, alongside Klarna, Affirm, Afterpay and WeGetFinancing, using a single integration.

How is Splitit different from other BNPL providers? Splitit splits a purchase across the customer’s existing credit card rather than issuing new credit, so there’s no application and no new credit line. That suits higher-ticket purchases and customers who don’t want another lending relationship.

Does offering more providers mean more integration work? No. Through a connector, each provider is a configuration change rather than a new build, certification, and settlement feed.

Can customers use these in-store? Yes. With tap-and-pay, a customer taps their phone on a chargeless tag and selects their provider — with no app download and no virtual card issuance, regardless of which provider they choose.

Which is best for high-ticket sales? Splitit and longer-term financing options generally suit high tickets better than pay-in-four products. Many retailers offer both tiers.

Does this work across all Dynamics 365 modules? Yes — Business Central, Finance & Operations, and Commerce.

Cover the providers your customers already use

The best BNPL provider is the one already in your customer’s pocket. One connector lets you offer all of them — online, at the register with no app friction, and by link.

Request a demo or see the full payment methods available through SensePass.