Business Central Payment Processing Options
Business Central Payment Processing Options helps Microsoft Dynamics 365 Business Central buyers compare payment processing extensions and gateway approaches using practical implementation criteria: processor choice, card-present devices, manual or phone card entry, e-commerce cards, payment portal fit, ACH, mobile payment options, recurring payments, preauthorization, reconciliation, and visible SaaS pricing.
Solution Overview
Payment processing in Business Central can range from a focused gateway connection to a deeply embedded receivables workflow. The System Solutions LLC payment documentation describes credit card, debit card, ACH, preauthorization, card-on-file tokenization, automatic payment, receipt, signature, LS Express, and reconciliation workflows in Business Central. Public vendor pages for iSolutions, Red Maple, EBizCharge, Versapay, and USTPay describe different levels of payment acceptance, AR automation, portal, processor, and reconciliation functionality.
This page is intentionally factual and feature-based. It does not rank vendors or make unsupported claims about product quality. It separates capabilities that are publicly documented from items that should be verified in a sales, implementation, or processor-selection discussion.
Business Central Payment Processing Options Overview
The right payment option depends on whether the business needs a processor-neutral embedded payment extension, a bundled processor and AR automation suite, a customer portal, card-present devices, ACH, recurring payment automation, interchange optimization, or a gateway-only architecture. Buyers should also confirm whether the vendor supports the exact processor, device, country, currency, portal, mobile method, and reconciliation workflow required.
For finance and operations buyers, the most useful comparison is not a broad marketing checklist. It is a workflow checklist: where the payment starts, how the card or bank account is entered, whether Business Central posts the cash receipt and customer ledger entries automatically, whether saved payment methods are tokenized, and how finance users reconcile merchant activity.
Business Central Payment Processing Options Features to Compare
- Processor choice and whether the buyer can keep an existing merchant processor.
- Card-present device support, including EMV, contactless, swipe, supported terminal families, and POS fit.
- Phone or manual card entry for card-not-present payments.
- E-commerce card support and whether online transactions flow back into Business Central.
- Customer payment portal and payment-link options.
- ACH and recurring ACH payment support.
- Mobile payment, wallet, text-to-pay, or customer-facing mobile payment scenarios.
- Preauthorization holds on sales orders, capture, void, and receipt workflows.
- Reconciliation, batch review, document matching, and reporting support.
- Annual SaaS price visibility and whether pricing is public or quote-based.
Business Central Payment Processing Options Selection Criteria
Use the Business Central Payment Processing Options comparison below as a qualification tool. A buyer choosing between System Solutions LLC, iSolutions, Red Maple, EBizCharge, Versapay, USTPay, and gateway-only approaches should ask each vendor to confirm the specific transaction paths the business actually uses.
| Criteria | Why it matters |
|---|---|
| Processor freedom | Determines whether the business can keep negotiated processor rates or must use a bundled processor model. |
| Device support | Important for counter sales, wholesale counters, card-present retail, and signature capture workflows. |
| Phone/manual entry | Important for mail order, phone order, and accounts receivable staff taking payments from customers. |
| E-commerce and portal | Important when customers self-pay invoices, use payment links, or pay orders online. |
| ACH and recurring payments | Important for lowering card costs, collecting balances automatically, and supporting payment plans. |
| Reconciliation | Important for matching authorized transactions, customer ledger entries, deposits, and batch/processor activity. |
| Price transparency | Important because some products publish subscription amounts while others require a quote. |
Business Central Payment Processing Options Comparison Matrix
Important: This table summarizes publicly available information and System Solutions documentation. Items marked as verify are not negative claims; they are due-diligence questions where public sources did not clearly document the exact capability.
| Option | Publicly documented functions | Choose own processor? | Devices | Phone/manual cards | E-commerce cards | ACH | Payment portal | Mobile payments | Annual SaaS price if known | Best-fit evaluation note |
|---|---|---|---|---|---|---|---|---|---|---|
| System Solutions LLC | Credit/debit card, ACH, sales invoice and credit memo payments, customer account payments, card-on-file tokenization, automatic payments, sales order preauthorization, receipts, signatures, LS Express integration, surcharge/cash discount options, reconciliation review, customer/payment portal options. | Yes. Public materials describe compatibility with major processors through Datacap in the U.S. and Canada. | Yes. Public AppSource text lists EMV chip, EMV contactless, swipe transactions, and compatible devices including Ingenico, Verifone, PAX, and ID Tech. | Yes. The user guide documents Pay API card entry directly in the payment page, and manual card entry options are documented for device workflows. | Supported through System Solutions Customer Payment Portal/payment link workflows; e-commerce/gateway options depend on the portal and gateway setup. | Yes. Public materials describe ACH and recurring ACH support when configured. | Portal supports online payments and payment links; payment portal support is separate from the core payment processing extension. | Mobile-style payments depend on the portal/gateway and contactless device setup; confirm exact wallet/device requirements for the processor. | See System Solutions Credit Card Processing Plans & Pricing on Microsoft AppSource for current subscription pricing and plan details. | Strong fit when processor choice, in-ERP posting, device support, ACH, preauthorization, LS Express, and reconciliation are important. |
| iSolutions | Public Marketplace text lists credit card and ACH processing, recurring payments, credit card reconciliation, click-to-pay links, enhanced email actions, API integration, Level 2/3 transactions, collections management, and customer portal. | Processor choice not clearly stated in public Marketplace snippets reviewed; verify merchant account/processor model with iSolutions. | Point of Sale package publicly listed on G2; public home page references Clover integration. | Public marketplace states authorize, capture, reverse transactions in Business Central documents; specific phone/manual card entry capabilities should be verified. | Marketplace and vendor pages mention e-commerce/API and click-to-pay capabilities. | Yes. Public Marketplace text lists credit card and ACH processing and recurring payments. | Yes. Public Marketplace text includes a customer portal with invoice payment and account history capabilities. | Not clearly documented in the public sources reviewed; verify mobile wallet, mobile terminal, or mobile portal requirements. | G2 lists iPayments Basic at $350/month, Advanced at $500/month, and Point of Sale at $150/month. Annual equivalents are $4,200, $6,000, and $1,800 before any negotiated fees. | Strong AR automation and customer portal positioning; verify processor flexibility and card-present hardware details. |
| Red Maple | Public AppSource text describes credit cards, ACH, PayPal, card present, card not present, e-commerce, call center, multiple cards per transaction, automated payment-to-invoice, customer portal, Level II/III processing, PCI 4.0 tokenization, and no Red Maple transaction fees. | Yes. Public AppSource text states that users can keep an existing processor or choose from 15+ supported options. | Yes. Public pages describe card-present processing and EMV/processor-device support. | Yes for card-not-present/call center scenarios based on public Red Maple materials. | Yes. Public AppSource text includes e-commerce. | Yes. Public AppSource text includes ACH. | Yes. Public text references Clever Division customer portal for self-service payments. | Not specifically confirmed in the public sources reviewed beyond card-present/e-commerce/channel support; verify mobile requirements. | Public Microsoft Marketplace uses Contact me; no public annual SaaS price found in reviewed sources. | Strong fit for processor flexibility, omnichannel credit card/ACH, customer portal, and mid-market processor choice. |
| EBizCharge | Public EBizCharge pages describe embedded payments, email pay, payment portal, recurring billing, auto pay, mobile pay, payment reminders, cash application, fraud prevention, reporting, and integrations with ERP/accounting/e-commerce/CRM/POS systems. | EBizCharge describes itself as a payment processor at its core; public sources reviewed do not position it as bring-your-own-processor for Business Central. | Public EBizCharge pages list POS as a supported channel. Specific Business Central device models should be verified. | Payment acceptance and recurring billing are public; specific Business Central phone/manual entry details should be verified. | Yes. Public pages describe e-commerce integrations. | Yes. Public pages describe ACH and electronic checks. | Yes. Public pages describe payment portal and email pay. | Yes. Public pages list Mobile Pay. | Official pricing page says pricing is customized and public pages emphasize no contracts, $0 hidden fees, and $0 unlimited support. No public annual SaaS subscription amount found. | Strong fit for organizations that want a bundled processor/payment platform with broad AR payment channels. |
| Versapay | Public Versapay pages describe Microsoft Dynamics payment acceptance across e-commerce, point of sale, and AR, click-to-pay invoicing, interchange optimization, Level 3 data processing, fraud management, omnichannel payments, auto-reconciliation, hosted payment pages, and shopping cart integrations. | Public pages reviewed emphasize Versapay payment integration and merchant services; processor choice should be verified with Versapay. | Yes. Public AppSource text says chip and PIN/EMV capable and Versapay page lists point of sale. | Public AppSource says payments/refunds are handled inside Dynamics; specific phone/manual card workflow should be verified. | Yes. Public pages mention e-commerce and shopping cart integrations. | Yes. Public pages list ACH, checks, bank payments, credit, debit, and virtual card. | Yes. Public pages describe hosted pages and online portals/reporting. | Not specifically confirmed as mobile wallet payments in reviewed public sources; verify mobile requirements. | Public Versapay page did not list standard annual SaaS pricing. Third-party pricing pages describe custom pricing; verify directly with vendor. | Strong fit for AR automation, omnichannel payments, interchange optimization, and Versapay-managed payment acceptance. |
| USTPay | Public AppSource text lists credit card, ACH/eCheck, hosted iframe fields, payment page, card verification, customer wallets, Level-3 processing, dynamic surcharging, payment links, customer invoice portal, POS options, recurring payments, and automation to post payments against invoices and GL accounts. | Yes. Public AppSource text states 140+ gateways/processors and Bring Your Own Processor. | Yes. Public AppSource text references POS options with Dejavoo Z-series or P-series terminals. | Hosted iframe/payment page/card verification are publicly documented; specific phone-entry workflows should be verified. | Gateway flexibility may support e-commerce use cases; public text focuses on Business Central, hosted payment page, invoice portal, and text-to-pay. | Yes. Public text includes ACH/eCheck and recurring card or ACH payments. | Yes. Public text includes customer secure link to pay and customer invoice portal. | Text-to-pay and payment links are public; verify mobile wallet/device requirements. | Public Marketplace provides free trial/contact style information; no public annual SaaS price found in reviewed sources. | Strong fit when gateway/processor portability and bring-your-own-processor are primary selection criteria. |
| Gateway-only approaches | Gateway-only approaches can connect Business Central to payment services, gateways, or custom integrations, but feature depth depends on the specific app, connector, middleware, or custom development. | Usually yes at the gateway or merchant account level, but Business Central feature depth depends on the integration layer. | Depends on the gateway and device integration; often not native without a specialized Business Central extension. | Depends on the gateway and integration design. | Often strong for e-commerce gateway use but may not automatically post and reconcile inside Business Central without integration work. | Depends on gateway support and connector design. | Depends on gateway-hosted payment page or portal provider. | Depends on the gateway, wallet, device, and custom implementation. | Varies by gateway. Authorize.net GatewayOnly states processor-neutral gateway setup but does not represent a complete Business Central payment extension on its own. | Best for organizations that want maximum gateway flexibility and are prepared to own integration scope, posting, reconciliation, and support. |
System Solutions Criteria for Business Central Payment Processing Options
For System Solutions LLC, the comparison criteria should include all documented payment-processing functions, not only basic credit card acceptance. The source guide and AppSource listing include customer payments, invoice payments, sales credit memo payments, automatic posting to customer ledger and general ledger, credit card, debit card, ACH, card-present device payments, card-not-present Pay API payments, cards on file, recurring card or ACH payments, sales order preauthorization holds, receipts, signatures, surcharge/cash discount options, LS Express integration, and transaction review.
In a Business Central Payment Processing Options evaluation, the System Solutions Customer Payment Portal should be treated as related but separate from the core Payment Processing extension. Public AppSource text for the portal describes online invoice payment, payment links, single or multiple invoice payments, tokenization, automatic ledger entries, credit/debit and ACH support, customer notifications, reminders, and compatibility with many gateways and payment methods.
Processor Choice in Business Central Payment Processing Options
Processor choice is one of the most important differences between Business Central Payment Processing Options. System Solutions public material describes compatibility with major processors using Datacap in the United States and Canada. Red Maple public AppSource text says buyers can keep an existing processor or choose from 15+ supported options. USTPay public AppSource text describes bring-your-own-processor and 140+ gateways/processors. Gateway-only approaches can also be processor/gateway flexible, but the Business Central integration depth depends on the connector or custom build.
By contrast, bundled payment platforms may provide strong automation and support but should be evaluated for processor model, gateway lock-in, merchant-account requirements, rate negotiation, token portability, and exit risk. This is not a reason to reject those platforms; it is a reason to ask direct procurement and implementation questions before selection.
Channel Fit for Business Central Payment Processing Options
Business Central Payment Processing Options should match the channel mix of the business. Counter sales and wholesale desks need device support. Accounts receivable teams may need phone or manual card entry. Online buyers may need e-commerce card acceptance or customer portal payments. Finance teams may need ACH and recurring payment options. Mobile requirements may mean contactless terminal support, customer payment links on a phone, text-to-pay, or mobile wallet support through a portal or gateway.
Because vendors use similar terms differently, confirm the exact workflow. For example, “portal” may mean an invoice self-pay portal, a customer account portal, a hosted payment page, or a payment-link page. “Mobile” may mean mobile-friendly customer payments, mobile wallets, text-to-pay, or a physical mobile terminal. “E-commerce” may mean a shopping-cart integration, API, portal checkout, or gateway connection.
Annual SaaS Price Visibility for Business Central Payment Processing Options
Public price visibility varies significantly across Business Central Payment Processing Options. In the public sources reviewed, iPayments pricing was visible on G2 as monthly package amounts. EBizCharge's official pricing page states that pricing is customized. Red Maple, Versapay, USTPay, and System Solutions public Marketplace sources reviewed used contact/trial/buy-now style information or did not expose a clear annual SaaS amount in the snippets reviewed.
When pricing is quote-based, the buyer should ask for the full first-year and renewal-year cost, including app subscription, implementation, support, gateway fees, portal fees, device costs, PCI fees, transaction add-ons, and processor costs. For gateway-only approaches, include the cost of Business Central integration development or middleware support, not just the gateway account.
Source Screenshot
The following preserved source screenshot shows the documented Credit Card Payment page used by the System Solutions payment processing workflow. It is included because payment option comparison should consider the actual Business Central payment user experience, not only provider marketing descriptions.
Example Business Workflows
Business Central Payment Processing Options for Counter Sales
A wholesale counter team needs a Business Central payment option that supports card-present devices, payment terminal setup by location or user, receipt handling, and automatic posting back to Business Central.
Processor Choice Evaluation
A controller wants to keep an existing merchant processor. The evaluation focuses on whether the payment option is processor-neutral, how many processors are supported, how card tokens are handled, and whether the business can change processors later without losing customer payment methods.
Invoice Payment Portal Workflow
An accounts receivable team wants to email payment links and allow customers to self-pay one or more invoices. The evaluation focuses on portal support, ACH, tokenized payment methods, automatic ledger entries, reminders, customer notifications, and customer-facing usability.
Recurring ACH and Card Workflow
A business wants to automatically collect recurring balances. The evaluation focuses on saved payment methods, recurring card or ACH support, authorization requirements, job queue or platform scheduling, and how failed payments are reviewed.
Finance Reconciliation Workflow
A finance team compares Business Central payment activity to merchant deposits. The evaluation focuses on authorized transaction review, export options, batch summary, card type subtotals, records without document numbers, and customer ledger posting behavior.
Public Source Notes
The following public sources were used to support the factual comparison. Vendor functionality can change, so buyers should confirm final capabilities, pricing, device compatibility, countries, and processor requirements directly with each provider before purchase.
- System Solutions Payment Processing
- System Solutions AppSource
- System Solutions Customer Payment Portal AppSource
- iSolutions Microsoft Marketplace
- iSolutions pricing on G2
- Red Maple AppSource
- Red Maple FAQ
- EBizCharge pricing
- EBizCharge platform
- Versapay Business Central
- Versapay AppSource
- USTPay AppSource
- USTPay Business Central overview
- Microsoft payment services
- Authorize.net GatewayOnly
Conclusion
Business Central Payment Processing Options should be evaluated by workflow fit, not by brand name alone. System Solutions LLC is a strong candidate when the buyer needs embedded Business Central postings, processor flexibility, Datacap-supported devices, ACH, cards on file, automatic payments, preauthorization, LS Express, receipts, signatures, and reconciliation review. Other options may be a better fit when the buyer prioritizes a wider AR suite, a specific portal model, a bundled payment processor, a particular supported processor network, or gateway-only control.
The safest buying process is to create a short transaction-script checklist and ask every vendor to demonstrate the same workflows: device sale, phone/manual card entry, posted invoice payment, e-commerce or portal payment, ACH payment, recurring payment, refund/void, preauthorization if needed, deposit reconciliation, customer ledger posting, and processor-change requirements.
Looking for additional Business Central Payment Processing information?
Visit our Business Central Payment Processing Page.
Looking for the Business Central Payment Processing User Guide?
Visit our Credit Card and ACH Processing for D365 Business Central User Guide.
View the Microsoft AppSource page for Business Central Payment Processing:
Business Central Payment Processing on Microsoft AppSource.