Global Payments Business Central integration

Global Payments Business Central integration

Global Payments Business Central integration helps a company retain a supported Global Payments merchant relationship while connecting card acceptance to customer, invoice, point-of-sale, saved-payment, recurring-payment, and accounting workflows in Microsoft Dynamics 365 Business Central.

Solution Overview

The System Solutions LLC payment extension connects authorized credit card, debit card, and eligible ACH activity with Business Central records. Supported workflows include customer payments, posted sales invoice and credit-memo payments, sales-order preauthorization and capture, tokenized cards on file, automatic payments, LS Express point-of-sale activity, receipts, transaction review, and accounting reconciliation.

Typical users include accounts receivable personnel, counter staff, finance teams, Business Central administrators, and implementation teams coordinating merchant credentials, payment methods, and certified devices.

Back to Table of Contents | Back to Top

Global Payments Business Central integration Overview

Global Payments Business Central integration Features

Global Payments describes its card-processing services as supporting major credit and debit card brands, contactless payments, digital wallets, gift cards, payment devices, tokenization, end-to-end encryption, Level 2 and Level 3 processing, cash discounting, and compliant surcharge programs. Review the official Global Payments card-processing page.

Its broader official site also presents payment solutions for in-person, online, integrated, and standalone use. For a Business Central deployment, the important step is to identify the merchant's exact Global Payments processing application before software credentials or devices are selected. Global Payments and Global Payments Portico are separately identified processing applications in current compatibility resources, so the processor name alone is not a complete deployment specification.

• Supports integrated in-person and card-not-present business workflows when the selected merchant setup is compatible.
• Offers secure processing features described by Global Payments, including PCI-compliant devices, tokenization, and end-to-end encryption.
• Supports payment-device choices that must be matched to the merchant account, processor application, encryption, and required Business Central workflow.
• Provides processor-specific merchant services while Business Central remains the operational system for invoices, customers, sales documents, and ledger entries.

Back to Table of Contents | Back to Top

Can I Keep My Existing Global Payments Processor?

Yes. A merchant already processing through Global Payments can pursue integration without automatically replacing the processor. System Solutions LLC connects supported Global Payments processing to integrated Business Central Payment Processing.

Before implementation, provide a current merchant statement and processor setup information. The review should confirm whether the account uses Global Payments or Global Payments Portico, together with merchant identifiers, locations, card-present and card-not-present requirements, existing payment tokens, terminal models, and encryption requirements. This prevents a processor name from being mistaken for a complete technical configuration.

Back to Table of Contents | Back to Top

Business Central Global Payments Credit Card Processing Questions

Is Global Payments Compatible With Business Central?

Yes. System Solutions LLC supports Global Payments. Review the Business Central payment-processing integration and verify the exact merchant application before deployment.

Is ACH Available?

Yes, when the applicable ACH account, authorization, and payment setup are in place. Review how Business Central ACH payments support invoice, customer-account, and recurring-payment workflows. ACH eligibility and setup should be confirmed for the merchant account rather than assumed from the processor name alone.

Can I Process Invoice Payments?

Yes. Accounts receivable users can collect payment from supported customer and posted-document workflows. See how to accept payments on invoices in Business Central.

Can I Use LS Express?

Yes, when the POS and payment deployment are configured together. Review LS Express POS for Business Central for the connected counter-sale workflow.

Can I Save Cards On File?

Yes, where the selected processing application supports tokenized cards. See how Business Central card-on-file processing saves approved payment methods as tokens for later use.

Can I Run Recurring Payments?

Yes, when the merchant setup, saved token, customer authorization, and Business Central schedule are configured. Review Business Central recurring payments.

Back to Table of Contents | Back to Top

Supported Payment Terminals

Terminal selection must match the exact Global Payments processing application, device certification, connection method, application load, encryption, and merchant requirements. The current compatible payment-device directory lists these device families and form factors for supported payment deployments. Not every model is automatically certified for every processor application.

Processor-Specific Device Examples

Current processor documentation specifically identifies device configurations for Global Payments on certain legacy and specialized models, including Verifone VX 820, Ingenico iCMP, and Ingenico iUC 285. Because availability and certification can change, these examples should be treated as implementation-review references rather than a purchase list.

Back to Table of Contents | Back to Top

Implementation And Compatibility Review

1. Collect merchant documentation. Obtain a current merchant statement and processor setup information.
2. Identify the processing application. Confirm whether the account uses Global Payments or Global Payments Portico.
3. Define workflows. List card-present, card-not-present, invoice, return, void, preauthorization, card-on-file, recurring, ACH, LS Express, receipt, signature, and reconciliation requirements.
4. Review saved tokens. Determine whether existing payment tokens require migration and whether suitable processor data is available.
5. Match certified hardware. Confirm the exact device model, application, firmware, connection, encryption, and availability.
6. Test in a sandbox. Validate authorizations, captures, returns, voids, posting, receipts, tokens, and reconciliation before production use.

This review keeps Business Central integration specific to the merchant account instead of treating “Global Payments” as a complete deployment specification.

Back to Table of Contents | Back to Top

Example Business Workflows

Existing Global Payments Merchant Moves To Business Central

The merchant supplies account information. The implementation team verifies the processing application, credentials, required transaction types, and terminal configuration before connecting authorized payments to Business Central records.

Counter Payment Applied To An Invoice

A counter user selects a customer or posted invoice, starts payment through the configured terminal, and completes EMV or contactless authorization. The result remains connected to the Business Central document for receipt and ledger review.

Sales Order Preauthorization And Capture

A user preauthorizes a Business Central sales order before fulfillment and follows the configured capture workflow when the order is invoiced.

Phone Payment Using A Saved Token

An accounts receivable user selects an approved tokenized card for a customer, processes a card-not-present payment, and applies the result to the correct invoice or account balance without storing raw card data in Business Central.

Recurring Customer Balance Collection

An authorized saved payment method and schedule are configured for an eligible customer. Automatic processing collects qualifying balances and records the results for Business Central review.

Back to Table of Contents | Back to Top

Conclusion

Global Payments Business Central integration gives supported merchants a path to retain an existing processor relationship while connecting card-present, card-not-present, invoice, POS, saved-payment, recurring-payment, and accounting workflows to Microsoft Dynamics 365 Business Central. The decisive implementation step is verifying the actual processing application, required payment functions, merchant credentials, and certified device configuration before deployment.

Back to Table of Contents | Back to Top

Related Resources

Back to Table of Contents | Back to Top