The Comdata tab displays the status of the Comdata Connection Service application running on the SC//AcuVigil™ edge security device (ESD). The Comdata Connection Service securely and reliably connects IP-based POS systems to Comdata's payment infrastructure via TLS relay tunnels. Use this tab to verify relay health, review transaction activity by terminal, inspect errors, and configure the service.
Application description: The Comdata Connection Service securely and reliably connects IP-based POS systems to Comdata's payment infrastructure.
Supported ESD models: MG3, SG1v1, SG2v1, XG1v1, VG
Layout
The Comdata tab has a standard app header and three sub-views: Transactions, Error Log, and Settings. The default sub-view is Transactions.
Header
| Element | Description |
|---|---|
| App icon | Comdata brand icon. Decorative. |
| Comdata Connection Service | App name / block title. |
| Subtitle | "The Comdata Connection Service app runs on Acumera's Merchant Gateway..." Static descriptor. |
| Version | Package version string (for example, Ver.R2A6z4). |
| Transactions | Link. Switches to the Transactions sub-view. |
| Error Log | Link. Switches to the Error Log sub-view. |
| Settings | Link. Switches to the Settings sub-view. |
Status banner
When a problem is detected, a colored banner appears below the header. Example:
CRITICAL: TLS - Comdata-usbank-0
The banner identifies the specific TLS relay that is in a CRITICAL state. Each relay is named after the Comdata service it carries (for example, Comdata-usbank-0, Comdata-multiservice-1). See TLS relay naming below.
Transactions sub-view
The default sub-view. Shows SmartSolutions transaction relay activity by hour.
Service note
At the top of the sub-view, a note identifies which Comdata services are enabled:
Both SmartSolutions and SmartSite services are enabled at this location.
Transaction data below is for SmartSolutions services only.
This note is site-specific. Sites with only one service type show a different message.
Summary line
N connections in the last 24 hours
Activity by hour table
Hourly breakdown of connection counts, newest-first, going back approximately 24 hours.
| Column | Description |
|---|---|
| Date | Date in MM/DD/YY format. |
| Hour | Hour of the day in 12-hour format. |
| Primary Ingress | Count of connections routed through the primary TLS relay ingress endpoint. |
| Backup Ingress | Count of connections routed through the backup TLS relay ingress endpoint. |
TLS relay timestamp
At the bottom of the sub-view:
TLS Relay started <time> on <date>
Indicates when the Comdata TLS relay session was last established. The relay must be running for transactions to pass.
Error log sub-view
Displays the last 50 Comdata application error log entries. When no log data is available:
No log data available.
Note. Unlike BUYPASS, whose error log shows "No errors in the log" when clean, Comdata shows "No log data available" for an empty log. This is the healthy empty state. |
Settings sub-view
Note: Scale Computing manages these settings as part of the managed service. You can view them here. To request a change, contact Scale Computing Support: open a ticket in the SC//AcuVigil dashboard, email team@scalecomputing.com, or call (512) 687-7401. |
Selects which payment processor relays are enabled at the site, for each Comdata POS type.
An info banner shows where the configuration comes from, for example:
Using company default configuration.
The view has two checkbox columns:
| Column | Description |
|---|---|
| SmartSite | Processor relays for the Comdata SmartSite POS. |
| SmartSolutions | Processor relays for the Comdata SmartSolutions POS. This column has a shorter list of options. |
A selected checkbox means the relay for that processor is enabled. Each column has a Toggle select all checkbox that selects or clears every option in the column.
The SmartSite column lists these processor options:
- Comdata
- DFConnect
- EFSLLC – TCH, EFS
- EFSLLC – Tchek
- FirstData Buypass Legacy
- FirstData Buypass RapidConnect
- Fleetcor-CFN
- FleetOne
- Heartland
- INTEVECON
- JP Morgan Chase
- Misc
- MultiService
- NBS
- Nitrogen
- US Bank
Most options also have a test variant, labeled with "- Test", that connects to the processor's test environment.
| Element | Type | Description |
|---|---|---|
| Update | Button | Saves the selection and applies it to the ESD. |
| Cancel | Button | Discards your changes. |
Warning: Selecting Update changes the configuration on the live site. Clearing a processor stops the site's POS from reaching that processor. |
TLS relay naming
Each Comdata terminal at a site is served by its own named TLS relay. Relay names follow this pattern:
Comdata-<service_name>-<index>
Examples: Comdata-22530, Comdata-multiservice-0, Comdata-usbank-0, Comdata-efsllc_tchek-0, Comdata-fleetone-0, Comdata-jbhunt-0, Comdata-nbs-0. The service name reflects the processor or fleet network option selected on the Settings sub-view. These names are processor and fleet network labels, not customer names. All relay sessions appear in the TLS Relays block on the Network Info sub-tab.
What to look for
- Status banner present — identifies which relay is degraded. The relay name in the banner maps to a specific entry in the Network Info TLS Relays block.
- Transactions count > 0 — confirms SmartSolutions relays are actively passing transactions.
- Primary Ingress vs. Backup Ingress — a shift from Primary to Backup traffic indicates the primary path degraded and fell over. Both returning to zero indicates the relay is down entirely.
- Error Log entries — "No log data available" is the healthy empty state for Comdata.