Which payment terminal is right for your business?

Start with where the payment happens

The form factor follows the physical situation, not the feature list. There are four practical shapes, and most businesses need one clearly and a second occasionally.

A countertop terminal sits at a fixed lane with mains power and a wired network. It is the fastest and most reliable option when the customer comes to a counter, and integrated receipt printing is usually part of the point. A mobile terminal is battery-powered with a cellular or Wi-Fi connection, and it exists so staff can take the payment to the customer: a table, a driveway, a job site, a market stall. A phone running Tap to Pay is the same idea with no extra hardware at all, at the cost of contactless-only acceptance. And a fully integrated point-of-sale setup treats the terminal as one part of a till that also handles items, tax, inventory and staff.

The mistake worth avoiding is buying for the exception. A restaurant that does ninety per cent of its volume at tables does not need a countertop unit at every station because of the occasional takeout order, and a retailer with two fixed lanes does not need a fleet of battery devices because of one sidewalk sale a year. Buy for the ordinary shift and handle the exception with the second device.

Connectivity, and what each option fails at

Every connectivity option works when everything is working. The choice is really about which failure you can live with during your busiest hour.

Ethernet is the most stable and the least flexible. It fails when the drop is in the wrong place, which is why a lane layout that changes seasonally is a poor fit for cabling. Wi-Fi is flexible and fails exactly when you least want it to: a full dining room, a busy retail floor and a venue with dozens of guest devices are all environments where the access point is congested at peak. Cellular is independent of your building but depends on coverage, and coverage inside a basement kitchen, a concrete stairwell or a rural service area is not the coverage you tested in the parking lot.

The practical answer for a fixed lane is Ethernet with Wi-Fi as a fallback, and for anything mobile it is cellular with Wi-Fi as a fallback. Check the reverse case too: ask what the device does when the connection drops mid-transaction. Store-and-forward behaviour, where the terminal captures the sale and settles it when the connection returns, is configuration-dependent and card-type-dependent. Do not assume debit behaves the way credit does, and get the answer for your card mix in writing before you deploy.

Battery life measured in shifts, not hours

A battery specification is only useful if you convert it into shifts. The question is whether one device covers a full service or a full route without leaving the floor, and whether the answer holds on a Saturday rather than a Tuesday.

Restaurants and field service stress a battery in different ways. A server carries the device continuously for six to ten hours, wakes the screen constantly, and prints or emails at every table, so the drain is steady all shift. A technician takes two or three payments a day but leaves the device in a truck in February, and cold is harder on a battery than usage is. Both cases are solved by planning charging rather than by chasing a bigger number: docks at the pass, a spare unit per section, a charger in the vehicle, and a rule about who plugs in what at close.

Also ask what happens to the device when the battery dies mid-transaction, how long a full charge takes, and whether the battery is serviceable. A terminal whose battery cannot be replaced has a shorter life than its warranty implies, and that shows up in the third year rather than the first.

Standalone, semi-integrated, or fully integrated

How the terminal talks to your other systems is the decision with the longest consequences, and it has three answers. Standalone means staff key the amount into the terminal and the till never knows about it. Semi-integrated means your point of sale sends the amount to the terminal and receives the result back, while the card itself goes from the reader to the processor without passing through the till. Fully integrated means the payment lives inside the point-of-sale application.

Semi-integrated is the arrangement worth understanding, because it is the one that keeps your point-of-sale system out of PCI scope. The till sends an amount and gets back an approval, a masked card number and a reference. It never sees the primary account number, so a compromise of the POS is not a compromise of card data, and your questionnaire does not have to cover the till. That is a meaningful reduction bought with a design choice rather than with a product.

Standalone is fine for low volume and terrible for reconciliation, because every sale has to be matched by hand and every mistyped amount is discovered at close. If the terminal needs to talk to a till, a kitchen display or an ERP, ask what the integration actually requires: a certified interface between the POS and the processor, a supported version of both, and a certification cycle that is measured in weeks rather than days. Where an existing hardware estate has to keep working across a processor change, APPIE is the interoperability layer built for exactly that, at the terminal or at the host.

PTS approval, and why an unapproved device is not a saving

A payment terminal has to hold PCI PTS approval for its point-of-interaction hardware, and that approval is public, model-specific and carries an expiry date. You can look up a device on the PCI Security Standards Council listing before you buy it, and you should, because the seller is not always the party who finds out.

An unapproved or expired device is not a cheaper terminal. It is a device your acquirer will not board, which cannot receive encryption keys, which is not certified for Interac debit with PIN entry in Canada, and which disqualifies you from the short card-present questionnaires that assume approved hardware. If it is compromised, you are the party holding the loss.

Second-hand hardware is where this bites most often. A terminal bought from a marketplace usually carries another merchant’s keys and another processor’s application, and reprogramming it may not be possible at all. Ask for the model name and the approval status before money moves, and treat a seller who cannot produce either as answering the question.

Prompts: tips, tap limits and PIN bypass

The prompts a terminal shows decide what you can prove afterwards, which is why they belong in the buying decision rather than in the setup call. Three of them matter.

Tip prompts differ in when they run. A tip taken on the device before the customer authorizes is part of the amount they approved, and the record shows it. A tip adjusted after authorization creates a gap between the authorized and settled amounts, which is normal practice in some environments but is also the most common source of a customer saying they never agreed to that number. If your business runs tip adjust, keep the signed record and expect to produce it.

Contactless verification limits decide when a tap needs a PIN. Below the limit the transaction completes with no PIN and no signature, so the evidence you hold is the chip cryptogram: strong proof the real card was present, and no proof at all about who was holding it. Above the limit the terminal asks for a PIN or an insert. PIN bypass is the third prompt, and it does the opposite of what its name suggests to your risk: allowing a cardholder to skip a PIN the transaction asked for turns a verified payment into an unverified one. Many merchants are better off having it disabled and never thinking about it again.

Receipts, and what they are actually for

A receipt is a dispute record before it is a courtesy, and the format you choose changes how easily you can retrieve it months later. Printed thermal, emailed, texted and no receipt at all are all legitimate answers for different businesses.

An integrated thermal printer is worth the counter space where customers expect paper and where a signature line still gets used. A mobile deployment usually goes digital, either through an optional Bluetooth printer or through email and SMS delivery from the device. Digital receipts have the advantage that the record is searchable rather than sitting in a shoebox, which is the version you want when a chargeback arrives sixty days later.

Whatever you choose, check three things: whether the receipt carries the reference you can use to find the transaction in reporting, whether a reprint is possible from the device and from the dashboard, and whether thermal paper for that model is a stock item or a special order. The last one sounds trivial until a Saturday.

Buying, renting, and reading the terms

Ownership and rental are both defensible; what decides the real cost is the contract, not the monthly figure. Buying puts the hardware on your books and the replacement risk with you. Renting keeps the upfront number low and, over a long enough term, costs more than the device.

Read for four things. The term and what happens at the end of it, including whether it renews automatically and how much notice cancellation takes. Whether the equipment agreement is with your processor or with a separate leasing company, because a lease signed with a third party is a different contract that can outlive the processing relationship entirely. What the device is locked to, since a terminal keyed to one processor is generally not portable to another. And what a failure costs: whether replacement is next-day or next-week, who pays shipping, and whether a damaged unit is repaired or billed.

Then add the recurring items that never appear on the sticker. Cellular connectivity on an LTE device is often a monthly line. Terminal rental, PCI non-compliance fees, and per-device charges appear on the statement rather than in the hardware quote. Hardware is priced separately from processing, so compare the two together or you are comparing halves.

The questions that surface the real cost

Ask these in the first conversation, and ask for the answers in writing. A salesperson who answers all of them plainly is telling you something useful about the rest of the relationship.

What is the model name, and is it currently PTS approved? Is the device certified for Interac debit with PIN in Canada? Is the quoted price purchase or rental, and if rental, what is the term, the renewal and the cancellation notice? Is the equipment agreement with you or with a leasing company? Is there a monthly connectivity charge on the cellular models? What is the replacement turnaround if a unit fails on a Friday, and who pays the shipping?

Then the operational half. Is the integration to my point of sale semi-integrated or fully integrated, and is it already certified or does it need a certification cycle? Can I run tip on device rather than tip adjust? Can PIN bypass be turned off? Does the terminal do store-and-forward if the connection drops, and does that answer differ for debit and credit? Can I reprint a receipt from the dashboard as well as the device? And what happens to this hardware if I leave — do I own it, return it, or keep paying for it?

Where RapidCents hardware fits

RapidCents supplies countertop, mobile and smart form factors on one merchant account, so a mixed estate reports as one business rather than as several. Devices connect over Ethernet, Wi-Fi or LTE, accept tap, chip and PIN debit, and sync to the merchant dashboard for transaction lookup, firmware updates and remote diagnostics.

The Rivo Go is the smart terminal shown on the payment terminals page: a full touchscreen device that takes tap, chip, swipe and manual entry, runs sales, tips, pre-authorizations, refunds and voids, carries Wi-Fi and cellular connectivity, and sits on an integrated counter stand inside an impact case. Countertop models pair Ethernet with Wi-Fi failover and an integrated thermal printer. Mobile models run on LTE with Wi-Fi fallback, take the tip on screen before the customer taps, and send receipts by email or SMS with an optional Bluetooth printer where paper is wanted.

Tap to Pay covers the case where the phone is the reader. It accepts contactless cards and wallets on supported iPhone and Android devices with no separate hardware, reports alongside terminal transactions, and requires a connection for authorization. It is deliberately contactless only: a customer with a chip-and-PIN-only card, or an Interac payment above the contactless limit, still needs a terminal. For an existing hardware estate that has to keep running across a processor change, APPIE on Terminal provides interoperability at the terminal layer without replacing the devices, and semi-integrated flows with certified point-of-sale partners cover the case where the till has to drive the lane.