Short answer: Dynamics 365 doesn’t support Klarna natively. You can add it either by building a direct Klarna integration for each channel you sell through, or by connecting Dynamics 365 once to a payment connector that already supports Klarna. The connector route is faster, covers online and in-store, and — with tap-and-pay — lets your customer pay with Klarna at the register without downloading the Klarna app or having a digital card issued.

This guide covers what Klarna acceptance actually involves in a Dynamics 365 environment, where the native paths get difficult, and how to run Klarna across every channel from one integration.

Why Klarna isn’t in Dynamics 365 out of the box

Dynamics 365 — whether you run Business Central, Finance & Operations, or Commerce — ships with payment connectors built around card acceptance. Most tie you to a single acquiring bank and a card-shaped set of methods.

Klarna isn’t a card. It’s a separate provider with its own API, its own session model, its own settlement cycle, and its own refund process. Adding it means integrating it — and then integrating it again for each channel and each sibling provider you want alongside it.

The three ways to add Klarna, compared

Direct Klarna integration Klarna via your PSP/terminal Via a payment connector
Development effort High — build against Klarna’s API Low, but vendor-dependent None — already built
Covers online Yes, if you build it Usually Yes
Covers in-store Separate build Only if the terminal supports it Yes
Shopper experience in-store QR scan → Klarna app, or digital single-use card Same Tap-and-pay — no app, no card issuance
Adding Affirm/Afterpay next Another full project Another vendor request Already connected
Reconciliation into D365 You build it Separate settlement feed Automatic

The in-store problem nobody mentions upfront

Online Klarna is well-trodden. In-store is where merchants get surprised.

Klarna’s native in-store flows generally mean one of two things for your customer. Either they scan a QR code at the register and complete the purchase inside Klarna’s flow on their phone — which needs a customer-facing screen, and static/printed QR codes need daily tampering checks — or they use a digital single-use card issued in the Klarna app and loaded into Apple Pay or Google Pay before they can tap.

Both work. Both also put a download-and-setup step between your customer and the sale, at the exact moment a queue is forming behind them. Staff end up talking shoppers through app installs, and a confused customer at a busy register costs more conversion than not offering Klarna at all.

There’s also an onboarding gate worth knowing: Klarna’s self-service in-store onboarding typically requires an established Klarna online history — a couple of months of activity and a meaningful number of captured orders — before you can enable certain point-of-sale features. If you’re new to Klarna, that route isn’t open to you yet.

How SensePass adds Klarna to Dynamics 365

SensePass is a payment connector: it links the Dynamics 365 environment you already run to 100+ payment methods and 50+ processors through a single integration. Klarna is one of them, already built and certified — so enabling it is configuration, not development.

Three things this changes in practice:

No per-provider integration. You connect Dynamics 365 once. Klarna switches on, and so does everything you add later — Affirm, Afterpay, wallets, ACH — without another project. Nothing changes inside your D365 environment.

In-store, with no app download. With tap-and-pay, the customer taps their own phone on a chargeless SensePass tag and pays with Klarna directly. No QR to scan, no Klarna app to install at the counter, no digital card to issue first. It’s the same experience they’d get checking out online, brought to the register — and it needs no dedicated terminal.

Every channel, one setup. Klarna works in your online checkout, at the register, and through pay-by-link for phone orders, quotes, and remote sales — all reconciling back into Dynamics 365 through the same pipeline.

Where Klarna earns its place

Klarna is worth offering when your basket sizes make a customer pause. It carries both pay-in-four and longer financing, which means it stretches from a $60 apparel order to a $2,000 furniture purchase, and it has genuine brand recognition with shoppers — many arrive already having an account.

For Dynamics 365 customers selling internationally, Klarna’s market coverage also matters: it’s one of the few BNPL brands recognized across both North America and much of Europe, which makes it a sensible first BNPL provider for a multi-market D365 estate.

Don’t forget the accounting half

Klarna pays you on a deferred, net basis — after deducting its fee, on its own settlement cycle — and refunds come back as deductions from a future payout rather than as separate credits. If you post a Klarna sale straight to a bank or cash account, your cash position will be wrong from the moment of sale.

The correct pattern uses a clearing account, settlement batch records, and matched fee and clawback postings. That’s covered in detail in BNPL reconciliation in Dynamics 365 — worth reading before you go live, not after your first month-end.

Frequently asked questions

Does Dynamics 365 support Klarna natively? No. Native Dynamics 365 payment connectors are built around card acceptance. Klarna requires either a direct integration, support from your PSP or terminal vendor, or a payment connector like SensePass that already includes it.

Can I accept Klarna in-store with Dynamics 365? Yes. Through SensePass tap-and-pay, a customer taps their phone on a chargeless tag and pays with Klarna at the register — with no app download and no digital card issuance, and no dedicated terminal required.

Do customers need the Klarna app to pay in-store? Not with SensePass. Klarna’s own in-store flows typically involve scanning a QR code into Klarna’s app or issuing a digital single-use card into Apple Pay or Google Pay. The tap-and-pay flow removes that step.

Which Dynamics 365 versions does this work with? Business Central, Finance & Operations, and Commerce. The connector layer sits alongside your environment rather than inside it, so the setup is the same regardless of module.

How long does it take to enable Klarna? Because the integration is pre-built, enabling Klarna is a configuration step rather than a development project — typically days, not the weeks a direct API build requires.

Can I add Affirm or Afterpay later? Yes, and that’s the main argument for the connector route. Affirm, Afterpay, and Zip, Sezzle and Splitit run through the same connection — switching one on doesn’t mean starting over.

How do Klarna refunds work? Klarna refunds follow Klarna’s own return process rather than a standard card refund, and settle as adjustments against future payouts. Reconciling them correctly means linking each adjustment to its originating transaction.

Get Klarna live in Dynamics 365

If Klarna is the first of several payment methods you expect to add, the integration decision matters more than the Klarna decision. One connector gives you Klarna online, at the register with no app friction, and by link — plus everything you add next.

Request a demo to see Klarna running in a Dynamics 365 environment, or explore the full Dynamics 365 payments picture first.