Short answer: Dynamics 365 doesn’t include Afterpay natively. You can integrate it directly, wait for your PSP to support it, or connect Dynamics 365 once to a payment connector that already has it. With a connector, Afterpay works online, through payment links, for ERPs via pay-by-link and in-store via tap-and-pay — without the customer setting up an Afterpay wallet card in the app first.

What Afterpay is for

Afterpay is the cleanest expression of pay-in-four: a purchase split into four interest-free installments, no long-term financing, no interest for the customer who pays on schedule. It skews to a younger, credit-averse shopper — the demographic that would rather not open a credit card at all — and it’s strongest in apparel, footwear, beauty, accessories, and specialty retail.

That makes it a natural fit for Dynamics 365 Commerce retailers with mid-range baskets: not the $3,000 sofa where Affirm earns its keep, but the $120 to $400 purchase where splitting into four payments removes the hesitation. Afterpay’s own merchant data has claimed substantial lifts in average order value and units per transaction where it’s offered — the mechanism is simple: four smaller numbers feel more affordable than one larger one.

The in-store friction: the Afterpay Card

Online, Afterpay is a checkout option like any other. In-store, its native model works like this: the customer opens the Afterpay app, taps the card icon to activate a digital wallet card, adds it to Apple Pay or Google Pay, and then taps to pay.

For a customer who already has the app configured, it’s smooth. For everyone else, it’s a setup process happening at your register — download, sign in, activate, add to wallet — while a queue builds. Retail staff end up doing tech support, and the shopper who was ready to buy is now troubleshooting a wallet.

This is the recurring pattern across every BNPL provider’s in-store solution: the mechanics get pushed onto the shopper’s phone at the least convenient moment.

How SensePass adds Afterpay to Dynamics 365

SensePass connects your existing Dynamics 365 environment to 100+ payment methods and 50+ processors through a single integration. Afterpay is already included.

Nothing to integrate. Afterpay is enabled by configuration, not development. You don’t build against its API, and you don’t wait on a terminal vendor’s roadmap. Your D365 environment is untouched.

At the register, no app setup. With tap-and-pay, the customer taps their phone on a chargeless SensePass tag and pays with Afterpay — no app install, no wallet card activation, no dedicated terminal. The in-store experience matches the online one, which is exactly what a shopper who knows Afterpay from your website expects.

Consistent across channels. Afterpay runs in your Commerce online checkout, at the POS, and through pay-by-link — so the customer who abandons a cart can be sent a link and still pay their way.

Why offering only one BNPL provider under-performs

Shoppers aren’t provider-agnostic. Someone with an established Afterpay account and a payment history isn’t going to open a Klarna account at your register — they’ll just pay another way, or not buy. Each provider carries its own installed base.

This is the practical argument for the connector model: because Afterpay, Klarna, Affirm, and Zip, Sezzle and Splitit all run through the same connection, offering four providers costs roughly what offering one does. With direct integrations, each additional provider is another build, another certification, another settlement feed to reconcile.

Accounting for Afterpay in Dynamics 365

Afterpay settles net of its merchant fee on a deferred cycle, and returns are deducted from future payouts. Posting the gross sale to cash at authorization will overstate your bank balance and leave an unexplained shortfall when the real deposit arrives.

Use a clearing-account architecture with settlement batch matching — the full pattern is in BNPL reconciliation in Dynamics 365.

Frequently asked questions

Does Dynamics 365 support Afterpay natively? No. Native D365 payment connectors are card-oriented. Afterpay requires a direct integration, PSP support, or a payment connector like SensePass that already includes it.

Can I accept Afterpay in-store with Dynamics 365? Yes. Through SensePass tap-and-pay, the customer taps their phone on a chargeless tag and pays with Afterpay at the register — no app setup and no wallet card activation required.

Do customers need the Afterpay app in-store? Not with SensePass. Afterpay’s native in-store method requires activating a digital wallet card inside the Afterpay app and adding it to Apple Pay or Google Pay. Tap-and-pay removes that step.

What’s the difference between Afterpay and Klarna? Afterpay is focused on interest-free pay-in-four. Klarna offers both pay-in-four and longer financing, and has broader international coverage. Many retailers offer both because their customer bases don’t fully overlap.

Does Afterpay suit high-ticket items? Less so. Pay-in-four works best on mid-range baskets; for higher tickets, longer-term financing from Affirm is usually the better fit.

Which Dynamics 365 modules are supported? Business Central, Finance & Operations, and Commerce.

Can I turn it off if it doesn’t perform? Yes. Because methods are enabled at the connector layer, switching a provider on or off is a configuration change rather than a de-integration project.

Give shoppers the provider they already use

The customer who has Afterpay set up will use Afterpay. The one with Klarna will use Klarna. One connector lets you offer both — online, at the register with no app friction, and in any link you send.

Request a demo or read the Dynamics 365 payments overview.