Practical guide · October 23, 2026

Payment terminals at multiple locations: a rollout checklist for merchants

Opening a second checkout location creates a coordination problem before it creates a hardware problem. A terminal can look ready while its store assignment, reporting access or support responsibility remains unclear. This checklist helps a Canadian merchant prepare a controlled rollout across branches, counters or temporary locations. It is a planning tool, not a promise that any particular account or terminal supports a multi-location setup.

Describe each location before requesting equipment

Create one row per operating location, even when the same person manages several stores. Record the address, opening date, checkout count, expected trading hours, connection options and the person who will receive equipment. Mark temporary sites clearly and describe whether devices are expected to move between sites.

Ask your processor how it will structure the accounts, store records and terminal assignments for your actual business. Do not assume that adding a terminal is the same as adding a store, or that an existing device may simply be moved. Keep the provider's confirmed mapping with your rollout plan. Leave passwords and customer card information out of the worksheet.

Use an assignment register

A descriptive counter name helps people talk about a device, but it does not replace the identifiers and account assignment confirmed by the provider. Keep those concepts separate in your internal record. Store the full administrative details securely and share only what each recipient needs.

Moneris' multi-terminal settings documentation illustrates why names and reporting options deserve explicit attention: that specific product offers terminal naming and multi-terminal batch-close settings. This does not establish that another model, a different provider or your account has the same features. Request instructions for the equipment actually supplied.

Start with one pilot location

Select a representative location and walk through receiving, installation, staff orientation and reporting before distributing a copied checklist to every branch. Ask the provider to define the permitted verification procedure and how any test transaction should be handled. Do not invent a live sale solely to see whether a device works.

Record the expected result and actual result for each check. Include whether the receipt identifies the intended business and whether an authorized manager can find the transaction in the intended reporting view. A successful screen at the terminal is only one part of acceptance. Have the responsible person investigate discrepancies before treating the pilot as complete.

Control physical handoffs

Use a simple delivery and handoff record: sender, recipient, date, device identity and condition. Check the delivered device against the expected record. The PCI Security Standards Council's guidance on protecting payment devices discusses protection against tampering and substitution, including periodic inspections and staff awareness. Follow your provider's procedures if anything looks unexpected; this worksheet is not a PCI compliance assessment.

Avoid a central “spare box” with no movement history. If a spare is needed, ask the provider what must happen before it is used at another counter or location. Record approval and the revised assignment rather than assuming every device is interchangeable.

Give each branch an opening and closing owner

Before launch, identify who can approve a configuration change, who can contact support, and who reviews unresolved transactions. Give staff the approved escalation route without distributing an administrator's password. Make the first shift's handover short: device location, approved operating instructions, responsible manager and known exceptions.

Use the end-of-day reconciliation checklist to structure closing questions, and keep the outage response worksheet available for interruptions. Confirm how your provider groups reporting before combining results across branches.

Define the decision to expand

Approve the next location only after the pilot's open questions have named owners and acceptable resolutions. Keep an exception log so a delayed shipment or unresolved reporting assignment is not hidden behind an overall launch date. For a discussion of equipment and account requirements, send PBH your operating requirements and request confirmation of available services and current terms for each location.