Payment Provider Configurations support how Counter Sales communicates with a payment provider. Each configuration holds the connection details (e.g., credentials and endpoint URLs) needed to authenticate and send payment transaction requests to the provider’s service.

Beyond connectivity, Payment Provider Configurations also control how Counter Sales selects which configuration to use for a given payment transaction. Settings such as Processing Order, Location Filter, and transaction type enabled (e.g., Manual Cards Enabled, Saved Cards Enabled, and Terminals Enabled) allow you to define when and where a configuration applies. This means you can have multiple configurations set up to handle different locations, transaction types, or business scenarios, and Counter Sales determines the appropriate one to use based on its payment provider selection logic.

You may have a single configuration to cover all your payment transactions, or multiple configurations tailored to specific needs. Either way, each configuration must be valid, enabled, and correctly set up to communicate with the payment provider before Counter Sales can use it.

Set up Payment Provider Configurations

1. Navigate to the Counter Sales Payment Provider Configurations page in Business Central.
2. Select New to open a blank configuration card.
3. Modify the following fields in the General tab:
   • Code: A unique name to identify this Payment Provider Configuration (e.g., EBIZCHARGE).
   • Type: Set based on the payment provider. The dropdown list populates based on which payment provider integration extensions are installed.
   • Description: Something meaningful to help users identify the configuration.
   • Enabled: Set to indicate whether the configuration is active. When set to Enabled, Counter Sales considers it in payment provider selection logic; when set to Disabled, it is skipped entirely.

4. Modify fields on the following tabs:
   • Connection Details: Stores the credentials and URLs required to communicate with the payment provider. These fields are conditional and vary depending on the specific payment provider integration. Refer to the payment provider’s documentation to understand which fields are required and how to populate them. Credential fields are masked for security purposes.
   • Processing: Controls how the configuration is included in the Counter Sales payment provider selection logic and which payment transaction types it supports. It includes the following fields:
     • Processing Order: The order in which this configuration is considered during the Counter Sales payment provider selection logic.
     • Location Filter: The specific location(s) this configuration applies to for a given payment transaction.
     • Manual Cards Enabled: Controls whether manual card transactions are supported.
     • Saved Cards Enabled: Controls whether saved card transactions are supported.
     • Terminals Enabled: Controls whether terminal transactions are supported.

• • The Payment & Card Details: Holds the default payment method and saved card reference details for the configuration. It includes the following fields:
    • Payment Method Code: The default, or fallback, Payment Method Code applied to the Payment Line created by the transaction. One must be set here as a fallback and may be required by the specific payment provider integration. If a matching payment network is configured in Payment Networks or Payment Provider Payment Networks, that Payment Method Code take priority; otherwise, the value set here is used.
    • Saved Card Source Table ID and Saved Card Source Table Name: The table that saved cards are linked and referenced against. Counter Sales standard business logic supports either the Contact (Id 5050) or Customer (Id 18) table.

• • Additional fields may appear on the Payment Provider Configuration card specific to the payment provider integration extension you have installed. Refer to that extension’s documentation to understand what those fields are, how they are used, and whether they are required.

Actions

The following actions are accessible on both the list and card pages:

• Test Connection: Once your Payment Provider Configurations is set up, use this action to confirm that the credentials and connection details have been entered correctly and the configuration can successfully communicate with the payment provider. The test is performed by the payment provider extension itself, so behavior may vary. Insight Works built extensions support this action. If the test fails, confirm the credentials and URLs are entered correctly.
• Log Entries: Opens the Payment Provider Log Entries page for entries created by the Payment Provider Configuration. A log entry is created each time a request is made to the payment provider, capturing details of that request. This can be useful for troubleshooting errors or reviewing a history of requests.
• Payment Networks: Counter Sales can identify the specific payment network, or card brand (e.g., Visa, Mastercard), used in a transaction and apply a corresponding Payment Method Code to the Payment Line. Refer to the Payment Networks documentation for more information.
• Terminals: Opens the list of terminals associated with the Payment Provider Configuration. Setup and management of terminals varies by payment provider. Refer to the relevant payment provider documentation for details.

Field reference

The following table lists the Counter Sales fields included in the Payment Provider Configuration: