System Solutions LLC Credit Card Processing for D365 Business Central User Guide

Extension

• Extension Version Number: 2.7.2.0
• Extension Version Date: 2/25/2026
• Published by: System Solutions LLC
• Find more extensions for Microsoft Dynamics 365 Business Central by System Solutions LLC

Description

The System Solutions Credit Card Processing extension allows Microsoft Dynamics 365 Business Central users to perform credit card, debit card and ACH payments to sales invoices and credit memos through Datacap NETePay platform. The extension also allows credit card Pre-Authorization holds to be performed on Sales Orders.  Please contact System Solutions LLC to make sure of the merchant services available for this service and compatibility with the Datacap NETePay platform.

Configuration

The below only shows the System Solutions Credit Card Processing configuration steps into Microsoft Dynamics 365 Business Central. Please be aware that it needs to have a verified merchant services and a card processing machine/device needs to be purchased to use its features fully, unless using the Pay API platform. Contact our sales team for more information: sales@syssolutionsllc.com  

Setting up the App

Payment Processing Setup page

Use the magnifying glass to search for the Payment Processing Setup page. Create and open a new record to start setting up the extension based on the fields described below. If you're using a PIN pad with the extension, additional settings can be found on the Payment Processing Terminals page and the EMV Param Download action will initialize the connection to it, as explained below.

• General
  
  • Payment Processing Code: Specifies the unique code for this payment processing setup. Multiple setup records can be created and assigned to specific logged in users.
  • Customer Payment No. Series: When payments are made through the Customer Payment page or preauthorizations, this number series is used for the document numbers. (Not needed if payments will only be made through POS.)
  • Customer Payment Journal Batch: When payments are made through the Customer Payment page or preauthorizations, this payment journal batch is used to post the payments. (Not needed if payments will only be made through POS.)
• Platform Connection
  • Credit Card Platform: The platform used to connect with Datacap: TranCloud, TranCloud (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 that corresponds with the Pay API platform linked to this setup. This must be specified to share tokens between the two platforms when using cards on file. Not used if the setup itself is Pay API or there are no other Pay API setups to connect it to.
• Options
  • Allow ACH Payments: For the Pay API platform, if ACH has been set up for the Datacap merchant, enable payments to be made with it.
    
  • Pay Immediately: The credit card page will automatically initiate a payment as soon as it opens. With this setting enabled, use the Cancel button to resend the transaction as a void or manual entry.
  • Close After Approved: The credit card page will automatically close after the transaction is approved and either a signature is required or is also approved.
  • Disable OK: When a PIN pad is used, the cardholder is normally asked to confirm the amount. With this setting enabled, it will skip this prompt.
  • Receipt Text: Instead of saving and printing the entire receipt text returned by Datacap, this setting allows only a small number of fields to be included to save space. "All Lines" will save the entire generated receipt. "Authorization Fields" include card number, Reference, and Auth Code. "EMV Fields" add Application Label, AID, TVR, IAD, TSI, ARC, and CVM. Not available with Moneris or Pay API.
  • Signature Not Required Below Amount: If signatures are accepted, sales below this amount will not require one, regardless of the verification method requested by the processor. (0 is the default value.)
  • Save Cards on File: Specifies whether accepted cards are saved on file to use with future purchases. All card data is securely tokenized and can only be used with payments under the same customer. "No Cards" disables the Card on File feature. "Optional During Payment" adds an option to the payment page that specifies whether the card should be saved on file or not. "All Cards" automatically saves accepted cards to the Card on File list.
  • Disallow Partial Authorizations: Sales must be authorized for the full amount or they will be declined.
  • Add Surcharge to Credit Card Sale and Surcharge Percent: Add a percent surcharge to each credit card sale. Laws regarding surcharges differ per region.
  • Waive Surcharge for Payments to Customer Account: When a payment is made directly to a customer's account, the surcharge will not be added to the amount paid.
• Preauthorizations
  • Preauthorizations can be enabled for sales orders, which are subsequently captured for settlement when the invoice is posted. For credit only (not debit).
    • Allow Sales Order Preauths: Specifies that preauthorizations can be made on sales orders. Currently, preauthorizations can only be enabled with the Pay API platform.
    • Max Amount Over Preauth: Specifies the maximum amount that a captured preauthorization can exceed the original preauthorized amount.
    • Void Preauth Without Capture: Specifies that a preauthorization can be voided without first being captured. Applicable when using First Data.
  • Receipts can be printed for Preauthorizations using the two installed Report ID's
    • When a user clicks Print Receipt it checks if any receipt data exists for the authorization.
      • If so, it uses Report ID 70371970, Extension Layout Default = Receipt data with payment header
      • Otherwise, it uses Report ID 70371971, Extension Layout default = Payment authorization receipt

• Moneris Canada
  • Merchant Language: Select either English or French.
  • Available Moneris transactions include:
    • Pairing and Un-Pairing of Devices.
    • Purchase.
    • Purchase Correction - This is a Void (entire amount); must be performed before the batch is closed.
    • Refund - Any point in time after batch is closed, must recall the past transaction number; full amount or partial amount for refund
    • Independent Refund - Refund any amount to the card (without referencing a specific transaction)
    • Force Post - Used if a card is authorized in a phone authorization (during outages is when phone authorizations are used)
    • Batch Close
    • Last 4 digits of card will be displayed on the receipt
  • Moneris transactions which are not available:
    • Tips
    • Surcharge
    • Cashback
    • Pre-Authorization
    • Mobile Card Processing Device
    • PinPad enabled Barcode Scanning
    • Processor based Gift or Loyalty programs
• Automatic Payments
  • Process Automatic Payments: Available for the Pay API platform, this allows customers to be automatically charged their balance on a monthly, weekly, or daily basis. A card must be on file for the customer. After enabling, entries will be added to the Job Queue Entries page, but will start with a status of "On Hold."
  • Automatic Payment Amount: When a customer's balance is paid with automatic payments, specify whether they should be charged the balance due or their full balance.
• Emailing
  • Emailing is currently only configurable for the Pay API platform.
  • Credit Card Emailing: An email will be sent to the customer after a manual credit card payment.
  • Automatic Credit Card Emailing: An email will be sent to the customer after an automatic credit card payment.
  • ACH Emailing: An email will be sent to the customer after a manual ACH payment. Emailing after ACH payments is a NACHA requirement.
  • Automatic ACH Emailing: An email will be sent to the customer after an automatic ACH payment. Emailing after ACH payments is a NACHA requirement.
  • Automatic Credit Card Payment Reminder Emailing: An email will be sent to the customer before a monthly or weekly automatic credit card payment is made.

  • Automatic ACH Payment Reminder Emailing: An email will be sent to the customer before a monthly or weekly automatic ACH payment is made.

• Text Templates
  • Text templates are used to customize emails and the ACH phone authorization script used by the Pay API platform.Fields can be inserted into the text as explained by the paragraph at the top.
  • Credit Card Email Subject: Specifies the subject of the email to send after credit card payments. The text can contain any of the listed tags to insert company, customer, or payment information into the email.
  • Credit Card Email Body: Specifies the body of the email to send after credit card payments. The text can contain any of the listed tags to insert company, customer, or payment information into the email.
  • ACH Email Subject: Specifies the subject of the email to send after ACH payments. The text can contain any of the listed tags to insert company, customer, or payment information into the email.
  • ACH Email Body: Specifies the body of the email to send after ACH payments. The text can contain any of the listed tags to insert company, customer, or payment information into the email.
  • Automatic Payment Reminder Subject: Specifies the subject of the email to send before credit card or ACH payments. The text can contain any of the listed tags to insert company, customer, or payment information into the email.
  • Automatic Payment Reminder Body: Specifies the body of the email to send before credit card or ACH payments. The text can contain any of the listed tags to insert company, customer, or payment information into the email.
  • ACH Phone Authorization Script: Specifies the default script to display for ACH phone authorizations.
• LS Express Integration
  • Add Exact Card Button: Adds "Exact Card" button to LS Express that trigger the Credit Card Payment for the exact amount. The Exact Card option should be turned off in the LS Express settings.

  • Copy Receipt to LS Express EFT Receipt: Copy the credit card receipt information to the LS Express' EFT receipt text, which allows the default POS slip to be used without modification.

  • Surcharge Item: If the surcharge option was enabled, select a non-inventory item that will be added to POS to represent the surcharge amount so it shows on the receipt.

• Testing Options
  • Use Test Account: Login to Datacap using SystemSolutionsTest account instead of SystemSolutions production account.
  • Show Req. and Resp. for Testing: A notification will show with the XML text for each request and response to help test issues. This would normally not be used.
• Actions
  • The Action buttons include tools to initialize and test connections. Some actions, such as EMV Param Download, are used with specific PIN pad devices, so it will ask you to select a payment terminal to determine which PIN pad to connect to.
  • EMV Param Download: Downloads information to the PIN pad device for the TranCloud or DC Direct platforms. This must be performed when the PIN pad is first installed or replaced.
  • Enable Test Mode: Turn on test mode with Datacap TranCloud. To turn it off, unplug the TranCloud device to reset it. Not normally used.
  • Get Devices Info: Shows a raw list of supported devices for the TranCloud platform. Not Normally used.
  • Check Devices Setup: Looks at device IDs entered on the User Setup page and checks them against the allowed devices (same list produced by Get Devices Info) for the TranCloud platform. Unknown devices will be labeled with "UNKNOWN DEVICE" and should be fixed on the User Setup page.
  • Signature Test: Use this to test communication with the PIN pad. Requests a signature and displays it on the screen.
  • Display On Device Test: Sends text to display on the PIN pad screen. DC Direct only.
  • Line Display Test: Sends text in the form of a line item to show on the PIN pad's line item display. DC Direct only.
  • Clear Line Display Test: Clears the PIN pad's line item display. DC Direct only.
  • Reset Display: Resets the PIN pad display.
  • Acquire Initial API Key: For the Pay API platform, use this to initialize your private API key with Datacap. This is must be performed when setting up the app for the first time.
  • Acquire New API Key: For the Pay API platform, reset your private API key.
  • Manually Set API Key: For the Pay API platform, manually enter your private API key. Be careful not to confuse this with the key received from Datacap, which should instead be added to the Datacap Pay API Public Key field.
• Related
  • The Related buttons open other pages from the Credit Card Processing extension.
  • Payment Terminals: Opens the Payment Processing Terminals page, which is used to set up terminals based on payment methods, locations, and users. The other settings on this page specify how each terminal connects to a PIN pad. See the section below for more information.
  • Authorized Transactions: Shows the list of authorized credit card transactions.
  • Batch Summary: This opens the batch summary page, which allows you to request a summary of the batch and close it. Automatic closing is usually set up, so this does not normally need to be done except for certain situations when advised by Datacap or the processor.
  • Pay To Customer Account: Opens the Customer Payment window to post a credit card payment to any customer.

Payment Processing Terminals page

A payment terminal corresponds to a specific setup used to process payments. For example, a register in a retail store needs to connect to a specific PIN pad device, or different payment methods might be associated with their own payment platforms. This is set up using the Payment Processing Terminals page, where payment terminals can be specified based on payment method, location, and/or Business Central user. Each record on this page must at least specify a Payment Method, which is used to make payments in Business Central, and a Payment Processing Code, which connects it to the settings set above. Location and User are optional based on how the payment terminals should be defined in the company.

• Payment Method Code: Specifies the payment method that is used to open the payment page with the payment terminal settings. The payment method must have a Bal. Account No. specified.
• Location Code: Specifies the location that is assigned to the payment terminal settings. Leave this field blank to specify default settings used for all locations.
• User ID: Specifies the user who is assigned to the payment terminal settings. Leave this field blank to specify default settings used for all users.
• Payment Processing Code: Specifies the payment processing setup to use with the payment terminal. This determines the payment platform, merchant ID, and other settings.
• PIN Pad Serial No. / Tran Device ID: Specifies, for the DC Direct platform, the serial number of the PIN pad used by the logged in user. For the TranCloud platform, specifies the Tran device ID used by the logged in user, overriding the comany's Tran device ID set on the setup page.
• PIN Pad IP Address: For TranCloud, the IP address of the credit card device. Get this from the device as explained in the Datacap setup guide.
• PIN Pad IP Port: For TranCloud, typically 12000, but 9599 with Moneris.
• PIN Pad MAC Address: Leave blank unless you want to connect to the device with MAC address instead of IP.
• Device: For TranCloud, also known as Secure Device ID. If the Datacap portal does not specify which device to use ("SecureDevice Provided by POS"), you can enter the Secure Device ID here. This allows each user to have its own device set for stores that have multiple types. Otherwise, if only one type of device is used in the store, leave this blank and set it in the Datacap portal.
• Terminal ID: The terminal ID if one was provided by the processor for the device. This can be left blank for most processors, but it's required for Moneris.
• User Merchant ID: If the user should use its own Merchant ID, set one here. Otherwise leave blank and it will use the merchant ID specified on the setup page.
• Line Display Auto Refresh: Specifies that the line display should be automatically refreshed to show the transaction amount and item information on the PIN pad. Used with the DC Direct platform. Currently requires the CC Processing and LS Express Integration extension.

Making the Payment

Making a Basic Transaction

After the payment is started, the Credit Card Payment window will open.

Amount shows the amount to be charged to the Credit Card. Use the Pay button to proceed and the credit card device will ask the customer to insert their card. Status will show the outcome of the transaction and the Approved field will show the total amount approved. In some cases, partial amounts may be approved and the amount paid will be adjusted accordingly. The Cancel button will cancel the current transaction being processed by the credit card device. Once a transaction is approved, click Close to continue the transaction.

With Pay API, the card can be entered directly into the Credit Card Payment page, no device is required.

ACH Payment

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

• A prearranged authorization method specifies that the customer has filled out an ACH authorization form for the payment or was recorded during a phone call authorizing the payment. An example ACH authorization form can be provided by System Solutions.
• A phone authorization method specifies that the customer will be read an authorization script over the phone. When this method is selected, the script will appear on the page with some details automatically filled in.
• Recurring payments are payments made from the account information on file. This can be set up to run automatically or by using the "Account on File" option (explained in the section below). Recurring payments must be explicitly authorized on the authorization form or in a recorded call. Using the form is more common for recurring payment authorizations. Once the form has been filled out, open the customer's Customer Card in Business Central and input the relevant ACH details. For more information, see the Setting Up Recurring ACH Payments With Pay API section below.

Other differences related to ACH payments include:

• Returns must have a previous authorization within 45 days selected.
• Voids must have a previous authorization from the same day selected.
• Returns cannot be voided.
• An email will be sent after the payment. This is a NACHA requirement.

Credit Card on File (Tokenization)

Use a card from the customer's saved cards instead of inputting new payment information. This option is named "Account on File" when making an ACH recurring payment.

Manual Card Entry

Under Options, Manual Entry can be enabled before clicking Pay to manually input the card number into the device. This option is not applicable to the Pay API platform, which is always manually entered. If the PIN pad automatically starts the payment process > Click 'Cancel' > enable 'Manual Entry' > Click 'Pay' > enter card information on credit card reader. Please note if setup on DC Direct using Ingenico Lane 3000 or 7000 the cancel must be completed on the Credit Card Reader itself (Red X)

• Credit Card Number
• Expiration Date
• Security Code
• Billing Zip Code

Device will prompt if card is chipped, say yes.

Making a Void

The Is Void option can be enabled before clicking Pay to process the transaction as a void. The type of the transaction is determined by the payment amount and this setting.

• Sale: Positive amount
• Return: Negative amount
• Void sale: Negative amount, Is Void enabled
• Void return: Positive amount, Is Void enabled

Capture Signatures

If the approved transaction requires a signature, the customer will be automatically prompted to sign. Status under the signature section will show if the signature was captured or not. Use the Show Signature button to show the signature on the page. If the signature needs to be captured again or if it needs to be manually retrieved at any time, the Sign button will also prompt the customer to sign.

Reviewing Authorized Transactions

Approved payments can be seen be searching Authorized Credit Card Transactions with the magnifying glass in Business Central, or through Related in the setup page. This list can be searched, sorted, or exported to Excel. For example, search or filter on the last 4 digits of an account card number to show its transactions. The following actions are available on the page:

• View Receipt: View and print the payment's receipt.
• View Signature: For the TranCloud or DC Direct platforms when signatures are enabled, view the selected payment's captured signature.
• View Email: For the Pay API platform with emailing enabled, view the email that was sent to the customer after the payment was completed.
• Filter Records Without Document No.: Filter the list to show any authorized payments that were not updated with a posted document.
• Assign Document No.: Manually assign a document number to the selected payment.

You can also see credit card payments made to specific customers, posted sales invoices, and posted sales credit memos by going to the relevant page > Actions > Payment Processing > View Payments.

Managing Customers' Cards on File

Set Up Cards on File

The Payment Process Setup field "Save Cards on File" specifies if cards should be saved to use with future purchases. If "All Cards" is selected, each approved card will be saved. If "Optional During Payment" is selected, the payment page will include an option to "save this card for future purchases," which, if enabled, will save the card used for the payment after it's approved. These saved cards can later be used on the payment page by selecting "Card on File" and selecting the card.

Cards on File With Multiple Platforms

If multiple credit card platforms or merchant IDs are set up in the extension, the tokens saved with the cards can be used across different merchants and platforms. In the Datacap portal, the merchant IDs must be set up with the same token sharing group to make this work.

Managing Cards on File

To manage a customer's cards on file, open the Customer card and go to Actions > Payment Processing > Cards on File. On this page, click delete to remove a card from the customer's list. The "Default" option specifies that the card should be selected automatically after "Card on File" is selected on the payment page. If automatic payments are enabled, an "Auto Payments" option will be visible, which allows you to specify which card should be used by the automatic payment.