Terminals

Overview

The TMS terminal area is the main operator workflow for viewing and managing ATM inventory.

Current Terminal Workflows

The current platform implementation supports these operator-facing workflows:

• list terminals and inspect terminal detail
• review telemetry and transaction activity
• inspect alerts, RMS command activity, webhook candidates, and RSS candidates
• assign connectors and routing policy
• generate provisioning exports for a terminal or fleet
• review provisioning job history before rolling forward or back
• move into the dedicated wireless workflow when carrier, WAN visibility, router inventory, or failover readiness needs a fleet-level view

Related APIs

The current published tenant-facing APIs are:

• GET /v1/portal
• GET /v1/transactions
• GET /v1/settlements

The broader live platform surface also includes:

• /v1/terminals
• /v1/connectors
• terminal provisioning exports and provisioning-job actions

Provisioning Guidance

Provisioning outputs should be treated as operator-controlled artifacts.

• keep exported configuration tied to a named terminal or group change
• review connector and routing assignments before distribution
• use rollback workflows when a provisioning push needs to be reverted
• retain job history so field changes can be traced later