Skip to main content
The Terminal Directory is a cross-merchant operations view available to Taliup HQ admins. It shows every terminal in your accessible scope — with ownership, activation status, device type, and catalog assignment — all in one paginated table. Use it to audit readiness, spot gaps (unactivated or catalog-less terminals), and navigate directly to a merchant or terminal record.
Terminal Directory full-page view with hero metrics, filter toolbar, and paginated terminal table

The Terminal Directory showing 10,571 terminals across all merchants, filtered to Activated status.

Access to this page requires an admin role. Super Admins see terminals across all ISOs. ISO users see only the terminals belonging to merchants within their ISO hierarchy.

​
Summary metrics

The hero panel at the top of the page shows three live counters that reflect the currently active filter scope:

​
Filters

Filter toolbar showing dropdown menus and the Apply filters / Reset filters buttons

The filter toolbar with Search, Sort, Rows, ISO, Status, and Catalog controls.

The toolbar exposes six filter controls. Changes are staged locally — click Apply filters to run the query and refresh the table. After adjusting one or more controls, click Apply filters to fetch results. Click Reset filters to clear all controls back to their defaults and reload. Active filters appear as labeled pills below the toolbar so you can see what is currently applied at a glance.
Active filters bar showing 'Status: Activated' pill and result count '1-25 of 10,571 terminals'

Active filter pills and result count shown below the toolbar.

​
Quick views

Four preset buttons let you jump to common views without manually adjusting individual controls: Each button displays a live count from the current summary. Clicking a quick view stages the filter change; Apply filters still runs the query.

​
Terminal table

The table lists one terminal per row. Each row shows the following columns:
Terminal row with name, TID, serial number, merchant name, location, device type, activation status, and catalog name

A single terminal row showing all seven columns.

The primary identifier label in the Terminal column switches automatically: PAX and Poynt terminals show TID, while AiOne and Castles terminals show Device ID.

​
Row actions

Click the ··· button on any terminal row to open its actions menu.
Actions dropdown with three items: Open terminal (with external link icon), View merchant (with store icon), and Delete terminal (in red with trash icon)

The actions menu for a terminal row, showing Open terminal, View merchant, and Delete terminal options.

​
Deleting a terminal

Deleting a terminal archives it from active use while preserving all historical references. The operation is not reversible from the directory — contact engineering if a deletion was made in error.
1

Open the actions menu

Click the ··· button on the terminal row you want to remove.
2

Select Delete terminal

Click Delete terminal in the actions menu. A confirmation modal opens showing the terminal name, its primary identifier, merchant, and location.
3

Review what will be removed

The modal lists what the deletion clears:
  • Staff assignments to this terminal are removed.
  • Catalog mappings and reader configuration are cleared.
  • If the terminal is Factor4-enabled, it is marked as Suspended in Factor4 before deletion proceeds (see note below).
Orders, transactions, and reports are not affected and remain fully intact.
4

Confirm

Click Delete terminal to proceed. The button shows “Deleting…” while the request is in flight. The modal closes and the row is removed from the table on success.
Deletion is permanent from the Terminal Directory. Staff assignments and catalog mappings cannot be recovered after the operation completes. Confirm with the merchant or ISO before proceeding.

​
Factor4 safety check

When the terminal’s location has an active Factor4 configuration, the confirmation modal displays a Factor4 Safety Check notice. In this case, the system suspends the terminal in Factor4 first. If that sync fails, the deletion is blocked and an error is returned — no data is changed.