Terminals

Open Store Operations > Terminals to review registered devices and payment readiness for the selected store. The page requires store.terminals.read. It is a merchant status and configuration view; adding, registering, or provisioning a terminal remains a Peak Support task.

On the Android register, catalog, customer, inventory, appointment, workforce, tax, and report screens use the current server feature-resolution flags. A terminal's provisioned role name does not independently grant or deny those screens. The register does not persist or replay privileged feature visibility. While current access is unresolved, new privileged navigation is unavailable; an already-open form retains its draft and camera callback but remains covered and noninteractive. A fresh denial closes that workflow. Draft ownership resets when the organization, store, or employee session changes. Visibility is refreshed for those changes and whenever the register resumes. PIN admission and server endpoint permissions still apply independently.

Temporarily unresolved access does not detach an already-admitted checkout customer or erase that sale's loyalty state. A fresh denial or scope/session reset can clear the association. Customer-ID lookups also recheck current feature availability at completion: a scan started before access was revoked cannot attach a customer afterward.

Review the terminal fleet

1. Confirm the selected store.
2. Open Terminals.
3. Review the fleet summary for online, offline, and total devices.
4. Review each row's:
   • terminal name and identifier;
   • Online, Offline, or Unknown status;
   • model and app version;
   • battery and storage, when reported; and
   • certificate expiration date.
5. Select Refresh when you need an immediate update. The list also refreshes automatically every 30 seconds.
6. Select a row to open the device detail.

The detail can include device identity, last-seen time, certificate status, battery, storage, scanner and card-reader connection, location, network information, uptime, memory, and registration timestamps. A value can be unavailable when the device has not reported it; that alone does not prove the hardware has failed.

Check Gateway status

The Gateway section is available only when the role also has store.transactions.read.

• If an account appears, review its authorization status and any displayed transit state.
• If the page says no Peak Gateway account is connected, payment setup is not complete for that store.
• If Gateway status cannot load, use Retry Gateway status after confirming the selected store and connection.

A user can have terminal read access without Sales & Payments access. In that case, the fleet remains visible but Gateway status does not.

Review payment configuration

Open a terminal row and find Payment Configuration. The detail identifies the configured processor and device mode when available.

The merchant-editable setting currently exposed here is Proxy timeout. Changing it requires store.terminals.admin; other terminal readers see the value read-only.

1. Confirm that you opened the intended terminal.
2. Review the current processor, device type, and proxy timeout.
3. Change the timeout only when your operating procedure or Peak Support directs you to.
4. Select Save configuration.
5. Reopen the detail and verify the saved value.

Store-wide receipt, tip, and gift-card behavior is inherited from checkout settings rather than configured per terminal here. EBT enablement is managed by Peak Support.

For Landi terminals, Peak Support selects NearPay on the POS itself or an external Nexgo reader. Selecting NearPay removes the external-reader pairing fields when the payment configuration is saved.

If the page says no payment configuration has been provisioned, contact Peak Support. The portal cannot create the missing configuration.

Understand POS price previews

On the Android register, locally displayed subtotals are provisional while the server checkout quote is pending. Cash and card prices come from the matching server quote; the POS does not apply a cached surcharge percentage to invent a card price.

For a split payment, enter the intended cash portion. The remaining card price is shown after cash acceptance and receipt of the server's residual quote. Until then, the split panel labels the amount as pending rather than presenting a locally calculated card remainder.

Troubleshoot an offline terminal

1. Select Refresh and confirm the status is still Offline.
2. Open the terminal detail and note Last seen.
3. On the device, confirm power and the network connection.
4. Check whether the scanner, card reader, battery, or storage detail points to a local device issue.
5. Restart the terminal and reopen the register application.
6. Wait for another fleet refresh and confirm whether the device returns online.

If every terminal is offline, check the store's router and whether another device can reach the internet. Follow the detailed steps in Troubleshooting.

Troubleshoot a payment issue

1. Confirm the terminal itself is online.
2. Review the Gateway status, if your role can view it.
3. Open the terminal and confirm that Payment Configuration exists.
4. Check that the card reader is reported connected when diagnostics are available.
5. Compare the issue with another terminal in the same store.
6. Retry a payment only after you have checked Sales & Payments for an existing result.

Contact Peak Support when:

• a new or replacement terminal must be added to the store;
• the page shows no payment configuration or no connected Gateway account;
• a certificate is expired or nearing expiration;
• EBT or another support-managed payment capability must be enabled;
• a terminal remains offline after power, network, restart, and refresh checks; or
• payment attempts remain unresolved after checking Sales & Payments.

Include the organization, selected store, terminal name and identifier, last-seen time, app version, Gateway status, approximate payment time and amount, and the exact message displayed. Never send full card numbers or security codes.