Chase Paymentech Business Central Integration

You are here:
Powerful Chase Paymentech Business Central Integration

Chase Paymentech Business Central Integration

Chase Paymentech Business Central integration

Chase Paymentech Business Central integration lets organizations use supported Chase payment-processing services with System Solutions LLC payment workflows in Microsoft Dynamics 365 Business Central, helping avoid a processor change solely to connect payment activity with ERP records.

Solution Overview

The integration is designed for businesses that want card-present and card-not-present payment activity connected to Business Central sales, customer account, accounts receivable, and point-of-sale processes. Typical users include accounts receivable teams, customer-service users, retail or wholesale counter staff, finance teams, and Business Central administrators.

Depending on the configured workflow, users can initiate payments from sales orders, customer cards, posted sales invoices, or LS Express POS, while Business Central records the related customer-ledger and general-ledger activity.

Back to Top

Can You Keep Your Existing Chase Paymentech Account?

Yes, when the merchant account and processing configuration are compatible with the supported Chase connection. The implementation team should verify the exact Chase platform, merchant identifiers, transaction types, and terminal requirements before deployment. This allows many businesses to preserve an existing processor relationship rather than changing processors simply to integrate payments with Business Central.

Back to Top

Chase Paymentech Business Central integration Compatibility

Chase Paymentech Business Central integration Features

Yes. System Solutions LLC supports Chase options within its Business Central Payment Processing solution. Available Business Central workflows include customer payments, posted invoice payments, card-present transactions, card-not-present transactions, sales-order preauthorization and capture, cards on file, recurring payments, and LS Express POS, subject to the selected Chase configuration.

Back to Top

Chase Payment Solutions Facts

Chase describes its merchant-services offering as Chase Payment Solutions. Chase's authoritative page presents payment acceptance for in-store, mobile, online, billing, and invoicing scenarios. It also identifies POS applications, readers, terminals, standalone terminals, payment links, virtual-terminal functions, and integrations as parts of its merchant-services portfolio.

Chase states that it serves more than 7 million small businesses and processed more than $2 trillion in payments in 2025. Chase also describes same-day deposits at no extra cost when eligible transactions are deposited to a Chase Business Complete Banking account. Requirements and availability should be confirmed directly with Chase.

Visit the official Chase Payment Solutions page for current processor, account, service, and product information.

Back to Top

Supported Payment Workflows

  • Customer account payments: Initiate a payment from the customer workflow and apply the payment to an account or selected document.
  • Posted invoice payments: Accept a payment for a posted sales invoice using the documented Business Central invoice payment workflow.
  • Card-present payments: Accept EMV chip or contactless payments through a supported payment terminal.
  • Card-not-present payments: Support phone-order and mail-order payment scenarios from Business Central.
  • Sales-order preauthorization: Authorize a sales order and capture the approved amount during invoicing when configured.
  • LS Express POS: Use the payment integration with LS Express point of sale for counter and retail transactions.
  • Cards on file: Save tokenized payment methods for approved future use through Business Central Card on File.
  • Recurring payments: Use stored payment methods in configured Business Central recurring payment workflows.

Back to Top

Is ACH Available?

ACH is available within the broader System Solutions LLC payment-processing solution when the merchant's selected payment platform and ACH setup support it. ACH availability should be verified separately from Chase card-processing compatibility because card and ACH services may require different onboarding and configuration. Review Business Central ACH Payments for invoice, customer-account, authorization, notification, and recurring ACH workflows.

Back to Top

What Payment Terminals Are Supported?

Terminal selection depends on the exact Chase processing connection, deployment architecture, required transaction types, encryption options, and device certification. The following device families are relevant candidates from the compatible-device catalog and should be confirmed for the specific Chase merchant configuration before ordering:

  • Ingenico Lane/3000, Lane/3600, Lane/7000, and Lane/8000
  • Ingenico Desk/3500 and Desk/5000
  • Ingenico Link/2500 and Move/5000
  • Ingenico DX4000, DX8000, EX6000, EX8000, RX5000, and RX7000
  • PAX A30, A35, A3700, A77, A800, A920 Pro, A920MAX, and Aries8
  • Verifone P200, P400, and M400
  • ID TECH VP3300, VP3350, VP6800, VP7200, and VP8300

Older Chase certifications also reference Ingenico Telium 2 smart terminals, Ingenico unattended terminals, and Equinox L5200/L5300 devices. These older models may be legacy equipment, so current availability and certification must be confirmed before procurement.

Back to Top

Frequently Asked Questions

Can I process invoice payments?

Yes. Payments can be initiated for posted sales invoices and recorded against the related Business Central customer and financial records. See Accept Payments on Invoices in Business Central.

Can I use LS Express?

Yes. The payment-processing solution supports an LS Express POS workflow for card-present counter and retail payments. See LS Retail LS Express POS.

Can I save cards on file?

Yes. The integration can use tokenized stored payment methods for approved future transactions. See Business Central Card on File.

Can I run recurring payments?

Yes. Configured automatic-payment workflows can use stored payment methods for recurring invoice or account-balance collection. See Business Central Recurring Payments.

Do I need to replace my payment terminals?

Not necessarily. Existing terminals must be reviewed for model, firmware, encryption, ownership, and certification compatibility. A supported device may still require configuration or replacement if it was provisioned for a different processing connection.

Back to Top

Example Business Workflows

Posted Invoice Payment

An accounts receivable user opens a posted sales invoice, starts payment processing, completes the approved Chase card transaction, and records the payment against the customer and invoice in Business Central.

Retail or Wholesale Counter Sale

A counter user completes an LS Express sale, presents the amount through a supported EMV terminal, and completes the card-present payment as part of the POS transaction.

Phone Order and Sales-Order Authorization

A customer-service user records a card-not-present payment or obtains a preauthorization on a sales order, then captures the authorization when the order is invoiced, subject to the configured Chase workflow.

Recurring Customer Balance Collection

A customer authorizes future use of a stored tokenized payment method, and the business uses a configured automatic-payment process to collect eligible invoice or account balances.

ACH Invoice Collection

When ACH is separately enabled and configured, an accounts receivable user collects an authorized bank-account payment and applies it to a customer invoice or balance through the Business Central ACH workflow.

Back to Top

Conclusion

Chase Paymentech Business Central integration gives Chase merchants a path to connect payment acceptance with Business Central invoice, customer account, sales order, recurring payment, and LS Express workflows. Final implementation planning should validate the merchant's exact Chase platform, account configuration, supported transaction types, and terminal certification before deployment.