How Do You Accept Credit Card Payments in Business Central?

Business Central doesn't process credit cards on its own. You accept card payments in Business Central by connecting a payment service: either the standard PayPal extension Microsoft ships with the product, or an embedded payments app that links Business Central to a gateway and a merchant processor. The right choice depends on how your customers pay, how much card volume you run, and how much of the posting and matching you want Business Central to handle without someone in AR stepping in.

That answer is accurate, but it skips the part that causes trouble later. Most teams pick a payment option during implementation, when the focus is on getting invoices out the door, and only find out six months after go-live what that choice costs them in fees, manual work, and flexibility.

What Business Central gives you out of the box

The built-in option is more capable than people expect for a first step. Once you turn on a payment service, Business Central adds a payment link to the sales invoices you email, and the customer clicks through to pay. Microsoft's guide to enabling customer payments through payment services notes that PayPal Payments Standard and WorldPay Payments Standard both come installed, although Microsoft has deprecated the WorldPay extension and plans to remove it. With a PayPal Business Merchant account, the PayPal Payments Standard extension can even register payments automatically, posting the entries and closing the invoice once the customer pays.

A small distributor sending forty invoices a month to customers who are comfortable paying through PayPal may never need more than that.

The gaps appear once cards become a real share of receivables. The standard extension sends customers away to a PayPal checkout page, and it isn't built for taking a card over the phone, running one at a counter, or charging a card on file for a recurring contract. It also ties you to PayPal's pricing. You can't bring the merchant account and negotiated rates you already have, which is usually the point where mid-market finance teams start looking at apps.

The three pieces behind every card payment

It helps to separate what happens when a customer pays by card, because vendors tend to blur these layers together. The blur costs money.

The gateway securely passes card details from Business Central, or from a customer payment page, out for authorization. The processor, backed by your merchant account, moves the money and sets your rates. The vault holds tokenized card data so you can charge a card again without anyone storing the actual number. Some payment apps bundle all three and own each one, while others let you choose your processor and keep the vault independent.

That distinction sounds academic until you try to switch providers. If the gateway owns your stored card tokens, leaving means asking every customer with a card on file to enter it again. Honestly, that's the moment most finance teams realize they were locked in, and it almost never comes up in the demo. Our piece on keeping your existing processor in Business Central walks through why separating these layers matters.

Where the real cost of card acceptance sits

Processing fees get most of the attention, and they deserve it. B2B card fees are not fixed, though. On commercial and purchasing cards, the interchange rate depends partly on the data you send with each transaction.

Visa changed that math this year. As PYMNTS reported, Visa's Commercial Enhanced Data Program phased out its Level 2 interchange program on April 18, 2026, and now rewards verified Level 3 data: line items, quantities, unit costs, and freight. Transactions that fail validation can be downgraded after the fact.

Business Central already holds most of that detail on the sales invoice, so the real question is whether your payment integration passes it to the processor. Many basic connectors don't, which is one reason Business Central users pay too much in processing fees without seeing why on their statements. Our guide to Level 3 data in Business Central covers the specifics.

The second cost is labor. When a payment lands outside Business Central, someone has to match it to the invoice, post a cash receipt, and chase the exceptions. Picture an AR specialist matching 300 card payments a month from a separate portal against open invoices. At two minutes each, that's ten hours a month spent on work an integrated setup handles by posting payments straight to the cash receipt journal.

The third cost is compliance. Every system that touches card data widens your scope under the PCI Data Security Standard, and tokenization keeps raw card numbers out of Business Central entirely. That's why we argue PCI compliance is an architecture decision rather than a box to tick after go-live.

What an embedded payments setup looks like day to day

A well-integrated app changes where the work happens. A collections clerk opens a posted invoice, takes a card over the phone, and Business Central applies the payment, posts the receipt, and closes the document without a second login. Customers who'd rather pay on their own get a link on the invoice that lands on a payment page tied to your Business Central data. A will-call desk can run cards on a physical terminal that reports back to the same ledger, and recurring customers get charged from a stored token on schedule.

None of this requires giving up the processor you already use, at least not with a gateway-agnostic app. Enterprise-grade payment solutions for Business Central let you connect your existing merchant account, keep your negotiated rates, and route different transaction types to different processors when that suits the business. Some, including USTPay, run entirely inside Business Central instead of through a separate portal, so AR stays in one system.

Not every company needs that much. A business taking a handful of card payments a quarter can live comfortably with PayPal links and a few minutes of manual matching. The harder question is where your own tipping point sits: at what volume does the time spent matching payments by hand cost more than the app?

How to choose the right approach

Start with how your customers actually pay. Pull six months of receipts and look at the split between checks, ACH, and cards, then separate consumer cards from commercial and purchasing cards, since the commercial share drives most of the Level 3 opportunity. After that, look at where payments come in: emailed invoices, phone orders, a counter, an online store, recurring contracts. Every channel your setup can't handle turns into a workaround somebody owns.

Next, ask your current processor two questions: what share of your commercial card transactions qualify for Level 3 rates, and how many get downgraded? The answers tell you whether the problem lies with your processor or with your integration. When you compare apps, ask who owns the card vault and what happens to stored cards if you leave. A vendor that hesitates on that one has told you something useful.

A practical next step

Before you talk to any vendor, map your payment channels and pull a recent merchant statement. That picture shows whether the standard extension will carry you or whether an embedded app will pay for itself within the first year. If a second set of eyes would help, the USTPay team is happy to walk through a statement with you and show where the fees are coming from.