Business Central Payment Gateway Integration

Business Central Payment Gateway Integration

Business Central Payment Gateway Integration helps Microsoft Dynamics 365 Business Central users connect payment gateway activity to invoice payments, customer account payments, ACH payments, card-on-file processing, automatic payments, sales order preauthorizations, payment terminals, authorized transaction review, receipts, and reconciliation workflows.

This intent page explains how a Business Central payment gateway fits into documented payment processing workflows for credit card, debit card, ACH, Pay API, TranCloud, DC Direct, Moneris Canada, LS Express, and account-receivable operations.

Solution Overview

Business Central payment processing workflows often involve more than a single card payment. A business may need to collect payments from posted invoices, accept payments at a counter, authorize ACH transactions, save approved cards for future use, run automatic payments, preauthorize Sales Orders, review receipts and signatures, and reconcile authorized transactions against processor deposit totals.

The System Solutions LLC Credit Card Processing functionality documented in the source guide supports these workflows inside Microsoft Dynamics 365 Business Central by connecting Business Central records and payment actions to Datacap-supported payment platforms and related payment terminal settings.

Typical users include accounts receivable staff, counter sales users, Business Central administrators, implementation consultants, and finance teams that need payment activity to stay connected to customers, invoices, credit memos, authorization records, receipts, and reconciliation review.

Back to Top

Business Central Payment Gateway Integration Overview

The documented extension allows Microsoft Dynamics 365 Business Central users to perform credit card, debit card, and ACH payments to sales invoices and credit memos. It also allows credit card pre-authorization holds to be performed on Sales Orders.

Business Central Payment Gateway Integration Features

• Credit card and debit card payments tied to Business Central sales invoices and credit memos.
• ACH payments through the Datacap Pay API platform when ACH is set up for the merchant.
• Payment Processing Setup records that define platform connection, payment behavior, receipt behavior, automatic payments, emailing, testing options, actions, and related payment pages.
• Payment Processing Terminals that can be specified by payment method, location, and Business Central user.
• Card-on-file tokenization for saved customer payment methods.
• Automatic payments using Business Central Job Queue entries.
• Sales Order preauthorizations that are captured when the order is posted to an invoice.
• Authorized transaction review, receipt review, signature review, email review, document assignment, and Analysis Mode reconciliation support.

Back to Top

Payment Platforms and Gateways

The Payment Processing Setup page includes a Credit Card Platform field that identifies the platform used to connect with Datacap. The documented options include TranCloud, TranCloud for Moneris Canada, DC Direct, and Pay API.

Platform settings include the Merchant ID, Tran Device ID for TranCloud, Datacap Pay API Public Key for Pay API, and Pay API Setup Code when tokens need to be shared between a Pay API setup and another platform setup.

The source documentation also identifies compatible processor names and explains that Moneris Canada has specific options and transaction availability. Moneris transactions documented as available include pairing and un-pairing devices, purchase, purchase correction, refund, independent refund, force post, batch close, and display of the last four digits of the card on the receipt.

Back to Top

Payment Processing Setup

The Payment Processing Setup page is used to create and open a setup record for the extension. The documented configuration includes general settings, platform connection settings, options, preauthorizations, Moneris Canada settings, automatic payments, emailing, text templates, LS Express integration, testing options, action buttons, and related pages.

Platform Connection and Gateway Settings

• Payment Processing Code: Specifies the unique code for the payment processing setup. Multiple setup records can be created and assigned to specific logged in users.
• Customer Payment No. Series: Used for document numbers when payments are made through the Customer Payment page or preauthorizations.
• Customer Payment Journal Batch: Used to post payments made through the Customer Payment page or preauthorizations.
• Credit Card Platform: Specifies the Datacap connection platform, including TranCloud, TranCloud for Moneris Canada, DC Direct, or Pay API.
• Merchant ID: Provided by Datacap.
• Tran Device ID: Provided by Datacap or printed on a label on the TranCloud device for the TranCloud platform.
• Datacap Pay API Public Key: Provided by Datacap for the Pay API platform.
• Pay API Setup Code: Specifies the Payment Processing Setup Code corresponding with the Pay API platform linked to this setup, which is required to share tokens between platforms when using cards on file.

Payment Behavior and Receipt Options

• Allow ACH Payments: Enables ACH payments for Pay API when ACH has been set up for the Datacap merchant.
• Pay Immediately: Automatically initiates a payment as soon as the credit card page opens.
• Close After Approved: Automatically closes the credit card page after approved completion conditions are met.
• Disable OK: Skips the PIN pad amount confirmation prompt when a PIN pad is used.
• Receipt Text: Controls whether the full receipt, authorization fields, or EMV fields are saved where supported.
• Signature Not Required Below Amount: Allows sales below a configured amount to avoid requiring a signature when signatures are accepted.
• Save Cards on File: Specifies whether accepted cards are saved as customer-specific tokenized payment methods.
• Disallow Partial Authorizations: Requires sales to be authorized for the full amount or declined.
• Add Surcharge to Credit Card Sale: Adds a percent surcharge when enabled. Surcharge laws differ by region.
• Waive Surcharge for Payments to Customer Account: Excludes payments made directly to a customer account from the surcharge.

Back to Top

Payment Processing Terminals

A payment terminal corresponds to a specific setup used to process payments. The Payment Processing Terminals page can define payment terminal settings by payment method, location, and Business Central user. Each record must at least specify a Payment Method and a Payment Processing Code.

An integrated payment gateway Business Central setup can use terminal records to route different payment methods, locations, or users to the correct payment platform, merchant ID, PIN pad, Tran Device ID, IP address, terminal identifier, or line display behavior.

• Payment Method Code: Specifies the payment method that opens the payment page with the terminal settings. The payment method must have a balance account number specified.
• Location Code: Assigns the terminal settings to a specific location or leaves the field blank for default settings.
• User ID: Assigns terminal settings to a specific Business Central user or leaves the field blank for default settings.
• Payment Processing Code: Connects the terminal to the Payment Processing Setup record.
• PIN Pad Serial No. / Tran Device ID: Specifies the DC Direct PIN pad serial number or TranCloud Tran Device ID.
• PIN Pad IP Address: For TranCloud, specifies the IP address of the credit card device.
• PIN Pad IP Port: For TranCloud, commonly 12000, or 9599 with Moneris.
• Terminal ID: Required for Moneris when provided by the processor.
• User Merchant ID: Allows a user-specific Merchant ID when needed.
• Line Display Auto Refresh: Used with DC Direct to refresh line item display information on the PIN pad.

Back to Top

Credit Card, ACH, and Card-on-File Workflows

Credit card payments can be initiated from several locations in Business Central, including the Customer Payment page, Customer Card, Posted Sales Invoice, Posted Sales Credit Memo, posting a sale, LS Express POS payment activity, automatic payments, and Sales Order preauthorization workflows.

After payment is started, the Credit Card Payment page opens. The amount shows the amount to be charged. The Pay button proceeds with the payment, the Status field shows the transaction outcome, the Approved field shows the approved amount, and the Print Receipt button can generate a receipt from an approved payment.

ACH Payments

ACH payments can be made using the Datacap Pay API platform. The documented workflow requires entry of authorization method, routing number, account number, and other account details. The authorization acknowledgment must be checked before proceeding, and ACH payments must be properly authorized.

The source guide documents prearranged authorization and phone authorization methods. Email is sent after ACH payments, and the guide notes that emailing after ACH payments is a NACHA requirement.

Card-on-File Tokenization

Card-on-file functionality allows a saved customer card to be selected instead of entering new payment information. The Save Cards on File setting controls whether no cards are saved, whether saving is optional during payment, or whether all approved cards are automatically saved.

Saved cards are managed from the Customer Card through Actions > Payment Processing > Cards on File. If multiple credit card platforms or merchant IDs are set up, saved tokens can be used across different merchants and platforms when the Datacap portal merchant IDs are set up with the same token sharing group.

Back to Top

Automatic Payments and Recurring Transactions

Automatic payments are available with the Pay API platform. When enabled, customers can be automatically charged their balance on a monthly, weekly, or daily basis. A card must be on file for the customer, and Job Queue Entries are added after the setup is enabled.

On the Customer Card, payment processing fields define the automatic payment schedule, prior automatic payment activity, and the selected card or ACH account enabled for automatic payments. Automatic payment jobs use Business Central Job Queue functionality and include monthly, weekly, and daily parameter strings.

Reminder emails for automatic payments can also be set up through Job Queue entries using monthly and weekly reminder parameters. The source guide documents that daily payments cannot use reminder emails.

Recurring ACH Payments

Recurring ACH payments can be performed automatically or by using the account-on-file option on the payment page. Recurring ACH payments must be explicitly authorized by form or recorded phone call. The authorization can specify frequency and amount limitations, which are entered on the Customer Card and checked before recurring ACH payments are made.

Back to Top

Sales Order Preauthorizations

Preauthorizations can be enabled for Sales Orders and subsequently captured for settlement when the invoice is posted. The source guide states that this is for credit only, not debit, and that preauthorizations can currently be enabled with the Pay API platform.

• Allow Sales Order Preauths: Enables preauthorizations on Sales Orders.
• Max Amount Over Preauth: Specifies the maximum amount a captured preauthorization can exceed the original amount.
• Void Preauth Without Capture: Allows a preauthorization to be voided without first being captured when applicable.
• Sales Order actions: Preauthorize, void preauthorization, review preauthorized amount, and print the last preauthorization receipt.
• Posted Sales Invoice actions: Void an uncaptured preauthorization, capture preauthorization, and print the last receipt for a captured preauthorization.

Back to Top

Reviewing and Reconciling Payment Activity

Approved payments can be reviewed by searching for Authorized Credit Card Transactions in Business Central or opening the list through the related action on the setup page. The list can be searched, sorted, or exported to Excel.

Authorized Transactions Review

• View Receipt: View and print the payment receipt.
• View Signature: View captured signatures for TranCloud or DC Direct platforms when signatures are enabled.
• View Email: View the email sent to the customer after Pay API payments when emailing is enabled.
• Filter Records Without Document No.: Filter payments that were not updated with a posted document number.
• Assign Document No.: Manually assign a document number to the selected payment.

The source guide also documents that credit card payments can be viewed from specific customers, posted sales invoices, and posted sales credit memos through Actions > Payment Processing > View Payments.

Processor Deposit Reconciliation

For reconciliation, the source guide documents using Authorized Credit Card Transactions Analysis Mode. A user can filter the list by payment date, save an analysis view, and add fields such as Card Type to display and subtotal by type such as Visa, AMEX, or Mastercard.

Back to Top

LS Express and Related Store Workflows

The source guide documents an additional CC Processing and LS Express Integration extension that integrates Credit Card Processing and LS Express. Through that integration, payments are made through LS Express payments at the point of sale, and credit card receipt text can be provided to the POS receipt slip through a report extension and alternative report layout.

Pay to Customer Account in LS Express can prompt the credit card page when using the configured payment method. Line item display can show POS items, total tax, and total amount on the PIN pad through the integration extension when enabled on the User Setup page.

The source guide also describes integration with Store Account Management Tools through the SAMT and CC Processing Integration extension. Store Account Management Tools can use the credit card device to accept signatures for house accounts or other payment types, and the last saved signature from a credit card transaction can be copied to Store Account Management Tools.

Back to Top

Example Business Workflows

Workflow 1: Invoice Payment Through a Business Central Payment Gateway

A Business Central user posts a sales invoice using a payment method configured in Payment Processing Terminals. The payment page opens, the payment is authorized through the configured platform, and the Business Central posting flow continues or stops based on the payment result.

Workflow 2: Customer Account Payment From the Customer Card

An accounts receivable user opens the Customer Card, chooses Actions > Payment Processing > Pay, selects an invoice if needed, and processes a credit card or ACH payment through the configured Datacap platform.

Workflow 3: Pay API Card-on-File or ACH Payment

A user saves an approved card on file or enters ACH account information with the required authorization. The saved payment method can then be used for future customer payments, automatic payments, or recurring ACH workflows according to the documented setup.

Workflow 4: Sales Order Preauthorization and Capture

A user opens a Sales Order, runs the preauthorization action for the order total, later posts the Sales Order to an invoice, and captures or prints the preauthorization receipt from the documented payment processing actions.

Workflow 5: Review and Reconcile Gateway Activity

A finance user opens Authorized Credit Card Transactions, reviews receipts, signatures, emails, and document assignments, then uses Analysis Mode to compare authorizations with processor deposit totals and group transactions by fields such as card type.

Back to Top

Conclusion

Business Central Payment Gateway Integration gives Business Central users a structured way to connect customer payment capture, gateway authorization, ACH processing, card-on-file tokenization, automatic payments, Sales Order preauthorizations, payment terminals, authorized transaction review, receipts, signatures, and reconciliation workflows.

For organizations evaluating a Business Central payment gateway, the key question is whether payment activity can stay connected to Business Central customers, invoices, credit memos, payment methods, terminals, authorization records, and finance review processes. The documented System Solutions LLC workflows show how these payment activities can be managed from Business Central records and related pages.