Do not add, reassign, or remove a terminal while any card-present request is sending, awaiting the customer, uncertain, or recovering. The Payments Hub terminal login is operational account information: never publish it in screenshots, CentriAI prompts, tickets, chat, or email. This screen stores a routing record; it does not provision the processor account, sign the physical device in, approve a webhook, or prove device connectivity.

Before you beginConfirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.

Step by step

  1. Before changing anything, confirm the CentriPOS business, physical location, register, device label/serial kept in an approved internal inventory, Payments Hub merchant/environment, terminal login currently signed into the device, and whether a payment intent is active or uncertain. Stop if any payment is unresolved.
  2. Go to Admin → Locations & Registers, identified by the Building2 icon. Open the exact location record and find Terminal Devices. Do not use a similarly named showroom, warehouse, or test location.
  3. Read the CentriPay™ Cloud notice. Merchant credentials, environment, public gateway key, application-source header, and webhook approval are configured for this location under Payanywhere Suite → Settings → In-Person Payments. Pairing below only creates the device-routing record.
  4. Wait for the terminal list to finish loading. No terminal devices paired is a completed empty state for the selected location; it does not prove that no physical terminals or processor logins exist outside CentriPOS.
  5. Choose Add Terminal. Enter a stable, human-readable Terminal Name that staff can distinguish during checkout, such as Front Counter A920—not a customer name, password, or full secret identifier.
  6. Enter the exact Payments Hub terminal login currently signed into that physical device. This value targets the correct device when multiple terminals share one MID. Verify it directly through the approved processor/device administration path; do not infer it from an email address or copy another location’s login.
  7. Understand the uniqueness rule before saving: CentriPOS upserts terminal records by the current tenant plus terminal login. Reusing an existing login updates/moves that terminal record’s name, location, type, register assignment, provider, and active state instead of creating a second independent pairing. Search existing locations first and document an intentional move.
  8. Choose Device Type: PAX (A920 Pro, etc.), Ingenico, or Other. This classification describes the paired device; it does not detect the hardware, validate firmware, or enable capabilities automatically.
  9. Optionally choose Default Register from registers belonging to the opened location. Choose No default register to make the terminal a location-level candidate. A register assignment is a routing preference, not exclusive ownership, and a supported checkout can explicitly override it.
  10. Review Terminal Name, login, Device Type, location, and Default Register, then choose Add Terminal once. The button requires a nonblank name and login. Wait for Terminal saved and confirm one row appears with the intended name, uppercase device type, login, and Paired register when assigned.
  11. Understand checkout routing priority for active CentriPay Cloud terminals: an explicit terminal selected at checkout wins; otherwise CentriPOS chooses a terminal assigned directly to the active register; otherwise it chooses an unassigned active terminal at the active location; otherwise it reports that no active terminal is available. A requested provider also filters candidates.
  12. When more than one candidate exists at the same priority, the resolver prefers the most recently seen terminal when last-seen evidence exists, then terminal name alphabetically. Do not rely on that tie-break as store policy—give each register an unambiguous assignment or explicitly select the device.
  13. To change an existing route, use its register selector. Choosing a register immediately writes the new register ID; choosing Unassigned immediately clears it. There is no confirmation or success toast for this selector, so wait for the query refresh and re-open/verify the location before testing.
  14. After reassignment, confirm that the chosen register belongs to the same displayed location and that no other active terminal creates an ambiguous same-priority candidate. The list includes all records for the location, but checkout uses active records only.
  15. To remove a pairing, choose Trash and read Remove this terminal? Confirm only when the exact device should no longer be routable. Removal hard-deletes the CentriPOS terminal-device record and then reports Terminal removed. It does not sign out the physical device, revoke processor credentials, cancel a merchant account, undo payments, or erase processor history.
  16. If a terminal is being moved, prefer a controlled update/re-pair plan over deletion during business hours. Because the login is the upsert key, adding it at the new location may update the existing record. Verify both old and new location lists afterward and ensure the old register no longer resolves to it.
  17. Run a controlled card-present test from the intended business/location/register with no customer-sensitive data. Confirm the checkout shows the expected terminal or explicit selector, the request reaches only that device, the amount matches, the terminal completes once, and CentriPOS records the expected approved/declined status.
  18. Test the fallback deliberately when relevant: remove the explicit selection and confirm the register-assigned device wins; for an unassigned location device, confirm it is used only when no register default exists. Never create a live duplicate charge just to test fallback.
  19. Trace a successful test through payment intent → terminal transaction → sale payment/receipt → register session → closure tender totals → processor batch → deposit. Device routing success alone does not prove settlement, webhook delivery, or accounting reconciliation.
  20. For no-device, wrong-device, duplicate, or uncertain behavior, stop retries. Capture the business/location/register, safe receipt or payment-intent reference, amount/time, expected terminal name, selected/resolved routing scope, masked processor reference, and displayed status/error. Check assignment, active state, provider, location credentials/environment, device login/connectivity, webhook, and existing terminal request before acting.
  21. The approved Amelia Grant Harbor & Hearth manifest contains only the safe Locations & Registers overview; it does not contain a location edit view or Terminal Devices form. This guide intentionally publishes without substituting that overview or inventing a terminal screenshot, and it never exposes the demo’s terminal login.

Screen and contract reference

Control or areaWhat it means
Building2 navigation iconExact Admin icon for Locations & Registers, where terminal routing records are managed.
CentriPay™ Cloud noticeSeparates location merchant/webhook configuration from terminal pairing.
Terminal DevicesAll paired terminal records for the opened location; checkout queries active records.
No terminal devices pairedLoaded empty state for CentriPOS records at this location, not processor inventory proof.
Add TerminalOpens the Add Terminal Device dialog.
Terminal NameHuman-readable operational label used to distinguish devices.
Payments Hub terminal loginExact device login and tenant-wide upsert key; restricted operational configuration.
Upsert behaviorSame tenant + login updates the existing record, potentially moving its location/assignment.
Device TypePAX, Ingenico, or Other classification; not hardware detection or capability validation.
Default RegisterOptional register-specific routing preference within the opened location.
No default register / UnassignedLocation-level terminal candidate used after explicit and register-default candidates.
Explicit checkout overrideHighest-priority active terminal choice when supported and provider-compatible.
Register defaultSecond priority: active terminal assigned directly to the current register.
Location defaultThird priority: active terminal at the current location with no register assignment.
Candidate tie-breakMost recently seen first, then terminal name; avoid relying on it for ambiguous routing.
Register selectorImmediate update with no confirmation or success toast; verify after refresh.
Trash / Remove this terminal?Confirmed hard deletion of the CentriPOS pairing record.
Terminal removedRouting record was deleted; processor/device account and historical payments remain.
Active stateOnly active records are eligible at checkout; this form does not expose an active toggle.
Controlled card-present testOne safe, authorized test proving routing and resulting CentriPOS/processor records.
Full payment traceIntent → terminal transaction → sale payment → register session/closure → batch → deposit.
No exact screenshotHarbor & Hearth safe captures do not include the Terminal Devices location-edit surface or any terminal login.

Expected result

The terminal reports the expected connection state and register assignment, and one controlled payment reaches only that selected device.

Troubleshooting

  • Check the processor transaction status before retrying an uncertain payment or refund.
  • Confirm the terminal, register, amount, and transaction reference all belong together.
  • Never include full card numbers or protected credentials in a support request.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.