Global Connect ONE brings fleet visibility, remote configuration, software delivery and support into one workspace for banks, acquirers and payment-service teams.
Go from fleet insight to action: know what is deployed, deliver the right software and configuration, and coordinate support from one workspace.
Inventory, assignment, connectivity and recent device reports in one operational view.
Target devices by serial, tag, location or merchant. Schedule software and configuration, then track execution.
See device context, coordinate tickets and service levels, and guide technicians through resolution.
Turn device data into faster decisions, controlled rollouts and coordinated service. Global Connect ONE brings terminal management, merchant operations and field support together in one workspace.
Read reported device identity and model, online status and last contact, network connections and IP addresses, geolocation, operating system, firmware, installed applications and versions. Battery level, mobile carrier and signal information add context where the device reports them. Spot connectivity problems and outdated software before planning an intervention.
Manage compatible Android and Linux devices through xTMSAgent. Organize your estate by device groups, tags and geographical divisions, then filter by merchant, location or serial number. Target the right devices for each operation while keeping each bank’s inventory and permissions separate. Available telemetry and controls depend on the device and its agent integration.
View and operate supported device screens remotely so support teams can inspect the terminal experience and guide troubleshooting without an immediate site visit. Remote desktop availability depends on the device platform and the remote-control capabilities it supports.
Browse permitted storage, change folders or enter a folder path, and upload or download files from the portal. Android access uses public storage; Linux access is restricted to approved locations. Compressed transfers reduce data use for compressible files, helping teams work over limited-bandwidth connections.
Select a compatible application from the device inventory and enable diagnostic logging for 1 to 72 hours. Logging stops automatically and uses bounded storage. Collect compressed logs under the device, review collections by date and application, and download files identified by device serial and collection time. Stop all compatible logging sessions or remove collected files from the portal when they are no longer needed.
Maintain an approved application catalog and make the right apps available to the right devices. Push application installations and updates over the air, target selected devices or fleet segments, and schedule tasks for a suitable deployment window. Track delivery and execution to see which terminals have completed the rollout and which need follow-up.
Deploy operational files to selected devices with destination-folder control, compressed delivery and task results. Coordinate scheduled deployments alongside application updates. Manage approved firmware releases and deliver OTA firmware updates to compatible device models, using device support and the relevant vendor integration.
Manage merchants, branches, locations and device assignments together. Combine merchant information with geographical divisions and fleet organization so operators can find the right terminal, understand its deployment context and apply changes to the intended part of the network.
Connect support tickets to merchants and devices, assign technicians, schedule service visits and maintenance, and follow work through resolution. On supported devices, users can create support tickets directly from the terminal, reducing the steps between an incident and a support request.
Configure merchant service-level agreements, monitor ticket priorities and deadlines, and plan technician workloads. Automatically calculate technician routes for scheduled visits using location information, then track visit progress. Give field teams the device context they need before arrival and keep support and operations working from the same information.
Version device settings and publish controlled revisions. Operators can select what changes while preserving each terminal’s existing configuration. The product views below come from a demonstration environment.
Choose which applications appear on each terminal, set their order, and configure navigation and status bar behavior from one bank-scoped workspace.
Start with a focused pilot: one device family, one merchant group and the workflows that matter most. We will define integration, rollout and success criteria together.