A checkout POS terminal does not touch card data itself; it hands the amount to a certified card reader. That one link decides speed, support and cost.
It is also the part of a lane specification that gets the least attention. Buyers spend weeks comparing processors and screen sizes, then discover at installation that the reader they intend to use needs a driver that is not in the software image, or a serial port that is already occupied, or a powered USB socket the terminal does not have. The connection between the till and the reader is worth settling before the order is placed rather than on the morning the lane goes live.
This guide works through the choices in the order they matter: who is responsible for the card data, whether the reader is integrated or separate, which interface suits which reader, and what to test before committing. The worked example is the BVS-SW156T2 dual-screen POS system, a 15.6-inch touch terminal with a second 15.6-inch customer panel, a Core i5 processor and 8 GB of memory, running Windows for standard retail and catering software.
1. Who Owns the Card Data
The single most useful thing to understand about card acceptance at a checkout is that a well-designed lane keeps the card data away from the terminal. The terminal sends the amount and a description; the reader prompts the customer, encrypts the card details at the point of entry, and returns an approval or a decline. The card number never lands in the till's memory or its log files.
That arrangement has three consequences buyers feel directly:
- ◆ Scope stays small. Where the reader encrypts at the point of entry, the terminal is generally treated as a conduit rather than a system that stores card data. Where the card details pass through the till application in the clear, the whole terminal enters the assessment scope instead.
- ◆ The reader is the certified part. It is the device that carries the payment certification, which is why it is usually bought from, or approved by, the acquiring bank rather than chosen from a hardware catalogue on price.
- ◆ Software updates are separate. Reader firmware and till software are two different maintenance tracks. A lane that cannot update the reader without a technician visit is a lane that will fall behind on scheme requirements.
2. Integrated or Separate: the Two Architectures
There are effectively two ways to put a card reader on a lane, and the choice changes almost everything downstream.
For most fixed lanes the separate reader wins, and not for technical reasons. It is the device most likely to be dropped, worn out or superseded by a scheme change, and having it separate means a reader can be replaced on its own, without touching the terminal. The terminal then only has to provide the right socket, which brings the question back to interfaces.
3. USB, Serial or Network: Picking the Interface
Four interface types appear on shop floors, and each has a signature behaviour when something goes wrong:
Keyboard-style USB is the easiest to install and the least predictable under pressure, which is why it tends to appear on low-volume lanes and gets replaced on busy ones. Serial is the most deterministic and the most demanding on setup. A terminal that offers both gives you room to change your mind later, which is the practical argument for counting ports carefully at specification time rather than buying the minimum.
The worked example carries six USB ports, two RS232 serial ports, RJ-45, VGA, line out and mic, so a lane can run a printer, a drawer, a scanner, a reader and still have a socket left for a scale or a second reader. That headroom is the whole point: on a real counter the fifth and sixth ports are usually occupied within a year.
4. Drivers, Port Numbers and Plug Order
This is where most lane installations lose an afternoon. The failure is rarely a broken device; it is an assignment that was never written down.
- ◆ Fix the port map on paper first. Decide which USB socket takes the printer, which takes the scanner and which takes the reader, then label the cables. A terminal with six ports has sixty possible plug orders, and only a few of them leave the payment application pointing at the reader.
- ◆ Assign serial ports explicitly. Serial devices enumerate in plug order on most systems. Naming the port in the payment configuration, rather than letting the software search, is what stops a reader being found on a different port after a service visit.
- ◆ Keep one image for the whole estate. If the spare terminal and the floor terminal run the same Windows build with the same drivers pre-installed, a swap is a five-minute job. If they do not, the spare is a project.
- ◆ Write the recovery step on the counter card. Most reader faults at a checkout are a cable or a power cycle. The person on the till should not need to call anyone to find that out.
5. Ports and Power on the Counter
A checkout is a chain of devices sharing one terminal's sockets and one wall supply. Getting the power budget right at specification time avoids the commonest call-out of all: a lane that resets when the printer and the reader work at the same moment.
Three rules cover most of it:
- ◆ Do not hang the reader off an unpowered hub. A reader that browns out mid-transaction leaves the sale in an ambiguous state, which is the worst possible outcome at a busy till.
- ◆ Give the terminal its own supply and its own socket. A 12 V/5 A adapter is a modest load, but it should not share a strip with a chiller or a coffee machine that cycles on and off.
- ◆ Wire the network where you can. A Gigabit socket for the terminal and a fallback wireless connection is the standard arrangement; relying on wireless alone turns an access point reboot into a closed lane.
Where the counter is genuinely short of sockets, the alternative is to stop adding boxes to it. A single-screen all-in-one such as the BVS-SJ156P1 POS terminal, which carries an integrated receipt printer, removes a printer and its cable from the counter entirely and frees a port for the reader.
6. What the Customer Sees While Paying
An external reader creates a small gap in the transaction: the operator turns to the reader and the customer turns to the same small device. A customer-facing screen on the terminal closes that gap, and it is the reason a dual-screen chassis is common at retail and catering counters rather than a decorative extra.
The panel has three jobs during payment, all of them about removing doubt:
- ◆ Show the basket as it is built. Price queries shrink when the line items are visible from the customer's side of the counter.
- ◆ Confirm the amount being authorised. The figure on the customer screen and the figure on the reader should be the same number at the same moment, and the customer is the person best placed to notice when they are not.
- ◆ Carry the waiting message. The short pause while a payment authorises is exactly when a promotional panel or an order summary earns its place.
Where the customer panel is the same size as the operator screen, the second display also doubles as a place to park the things that should not clutter the till: loyalty prompts, opening hours, the queue number at a food counter. The SW156T2 dual-screen POS system pairs two 15.6-inch panels, the BVS-SW156R2 dual touchscreen cash register uses a smaller 11.6-inch customer panel for compact counters, and the BVS-SW150R2 dual-screen POS machine covers the tightest positions of the three. Where a single screen is enough for the lane and the customer reads a printed receipt rather than a panel, the BVS-SW156T1 POS terminal covers that counter instead.
7. A Test Script Before You Commit
The reader-till combination should be tested as a pair, with the exact reader model you intend to deploy, before a lane depends on it. A short script covers almost everything that goes wrong in the first month:
Run that script at the counter, not on a bench, and with the software build that will ship. A lane is a system, and a system is only proven in its final state.
8. The Short Version
Keep the card data inside the certified reader and let the terminal be a conduit. For a fixed lane, choose a separate reader so that the part most likely to change is also the part you can swap on its own. Decide the interface deliberately — keyboard-style USB for simple low-volume lanes, a driver-based USB or a serial connection where the payment application needs a real error channel — then write the port map down and keep one software image across the estate. Count the ports before you count the peripherals, give the terminal its own power, and test the exact reader and terminal pairing with a refund, a split tender and a cancelled payment before a queue ever depends on it.
Our POS system collection lists the single-screen and dual-screen terminals that carry the port count this article describes, and the accessories range covers the printers, drawers and scanners that sit on the same counter. The popular stock configurations are a useful starting point for a first order. If your reader or your acquiring bank has requirements the catalogue does not obviously meet, tell us the model and the interface and we will confirm what the terminal needs to provide.
