1. Sector overview
Why hotel payments are a different animal from retail checkout.
In a shop, a sale is one card tap and it's over. In a hotel, a single guest stay can involve four or five separate money events: a pre-authorization (a temporary hold on the card) at check-in, incremental authorizations if the guest's spending grows during the stay, room charges posted from the restaurant, bar, or spa to the guest's folio, and a final settlement (capturing the actual amount) at checkout. If any link in that chain is misconfigured, money leaks: holds that never release, authorizations that expire before settlement, or folio postings that land on the wrong room.
The property management system (PMS) is the hub of everything. Reservations, room assignments, folios, and the night audit all live there — and the payment terminals talk to the PMS through a payment interface rather than acting as standalone checkout devices. That makes compatibility between your terminals, your processor, and your PMS vendor the single most important purchasing decision. A terminal that works beautifully in a retail store can be the wrong device for a front desk if your PMS vendor doesn't support it.
Two more hotel-specific realities shape every decision in this guide:
- Guests bring their own network expectations. Your property runs guest Wi-Fi, and that traffic must never share a network with payments, the PMS, or the outlet POS. Segmentation isn't optional — it's the difference between a contained network and a breach that touches every system.
- Payment costs sit outside your IT budget. Processing fees rarely appear in formal technology spending figures, which is why two hotels with identical tech stacks can have wildly different total costs. Any honest cost comparison has to include processing.
⚠️ Confirm terminal compatibility with your PMS vendor first
Before you change processors, buy terminals, or sign anything: ask your PMS vendor which payment terminals and processors their payment interface supports. An incompatible terminal means the pre-authorization and folio-settlement flow above simply won't work — and you'll discover it at the worst possible moment. Get the answer in writing, and while you're at it, confirm token portability (whether card tokens move with you if you change processors later) in writing too.
2. In-store hardware & software
The roles each piece of equipment plays at the front desk and across the property.
Front-desk workstation
The PC or terminal the front-desk team uses to run the PMS. Wired via Ethernet for reliability — this is not the device to put on Wi-Fi.
Countertop payment terminals
Ethernet-connected terminals at the desk that talk to the PMS through the payment interface. These handle pre-authorizations, incremental authorizations, and checkout settlement.
Mobile payment terminal
For the pool bar, valet, room service, or anywhere away from the desk. Runs over cellular or the property's operational Wi-Fi — never guest Wi-Fi.
Payment interface service
Software (usually on your property LAN) that connects the PMS to the payment terminals and the processor. If this goes down, the desk can't take cards — even if the terminals look fine.
Outlet POS
The restaurant, bar, café, or spa POS. It posts charges to the guest's room folio in the PMS rather than settling them independently — that's what makes it hotel POS rather than restaurant POS.
Receipt printer & cash drawer
Folio receipts at checkout and a drawer for the cash that still moves at most front desks. The drawer typically connects through the printer's cash-drawer port.
On the software side, the stack is: PMS (system of record) → payment interface (connects PMS to processor) → processor (moves the money). Around that orbit the booking engine on your website, the channel manager that syncs rates and availability to online travel agencies, and accounting software that receives summarized revenue from the night audit.
3. Sample setup: a 40-room boutique hotel
One workable layout for a small independent property. Scale the terminal count with your desk positions, not your room count.
Hardware list
- Front-desk workstation — one PC running the PMS, connected by Ethernet to the property LAN.
- Payment interface service — the PMS vendor's payment connector, running on the property LAN so the PMS and terminals can reach the processor.
- Two countertop payment terminals — Ethernet-connected, one per desk position, set up for pre-authorization and settlement through the PMS.
- One mobile payment terminal — cellular or property operational Wi-Fi for the pool bar, valet, or room service.
- Outlet POS — one station for the restaurant/bar, configured to post room charges to guest folios.
- Receipt printer + cash drawer — folio receipts at checkout; drawer triggered through the printer.
- Network switch + firewall — wired backbone for desk, interface service, and outlet POS; guest Wi-Fi on a fully separate segment.
Layout notes
- Put the front-desk workstation, payment interface, and countertop terminals on wired Ethernet. The desk is the worst place in the building for a Wi-Fi dropout.
- Keep the guest Wi-Fi network physically and logically separate from the PMS, POS, and payment networks — separate VLAN at minimum, with firewall rules blocking guest-to-operational traffic.
- Place the two countertop terminals so each desk position has its own — staff shouldn't be reaching across each other (or guests) with a card terminal.
- The mobile terminal lives on cellular or the operational staff Wi-Fi, charged at the desk between uses. Never pair it to guest Wi-Fi.
- The outlet POS needs a reliable path to the PMS for folio posting — wire it if the restaurant is anywhere near the network closet.
Daily workflow
- Morning: confirm the payment interface service and both countertop terminals are online before the first check-in.
- Check-in: run a pre-authorization for the room rate plus your incidentals policy amount.
- During the stay: run incremental authorizations as the guest's folio balance grows (restaurant, spa, room service) so the hold keeps pace with spending.
- Checkout: settle (complete) the folio for the final amount — this captures the actual total and releases the difference on the hold.
- Night audit: reconcile the PMS day totals against the outlet POS and the processor's settlement report. Investigate anything that doesn't match before it becomes tomorrow's problem.
4. Setup guide
The order that avoids expensive rework.
Start with the PMS
Choose or confirm your property management system first. Everything downstream — terminals, processor, integrations — must be compatible with it.
Get compatibility in writing
Ask your PMS vendor which processors and terminal types their payment interface supports, and confirm token portability. Written, not verbal.
Choose the processor
Pick from the PMS-supported list. This is also the moment to compare effective rates — a free statement audit tells you what you're really paying today.
Wire the property
Run Ethernet to the desk, the interface-service host, and the outlet POS. Set up the guest Wi-Fi as a separate, isolated segment from day one.
Install & configure
Set up terminals through the interface service, configure pre-auth amounts, incremental-auth rules, and folio posting from the outlet POS.
Test the full stay
Run a test reservation end to end: check-in pre-auth, a restaurant charge posted to the folio, an incremental auth, checkout settlement, and the night audit.
5. Install guides
Per-device installation notes. Always follow your PMS vendor's and processor's current documentation alongside these.
Countertop payment terminal (Ethernet)
Place one terminal per desk position within comfortable reach of staff. Connect Ethernet to your property LAN switch and power. Complete the processor's activation (usually a code on screen plus a confirmation in their portal), then link the terminal to the PMS payment interface — your PMS vendor provides this step. Run a small test authorization and void it, then confirm the transaction appears in the PMS. Label each terminal (Desk A / Desk B) so troubleshooting later is unambiguous.
Payment interface service
Install on a machine that stays on — a back-office PC or small server on the property LAN, not the front-desk workstation someone might reboot mid-shift. Give it a static IP or DHCP reservation, open only the firewall ports your PMS vendor specifies, and verify the PMS can reach it and it can reach the processor. Test a pre-authorization from the PMS; if it fails here, nothing at the desk will work.
Mobile payment terminal
Charge fully, connect to cellular or your operational staff Wi-Fi (never guest Wi-Fi), and complete processor activation. If it must work in the parking lot or poolside, verify signal strength at the actual spots staff will use it — not just at the desk. Set a home base at the front desk where it charges between uses, and confirm with your processor how mobile transactions settle alongside desk transactions.
Outlet POS with folio posting
Install the outlet POS per your POS vendor's guide, then configure the PMS link for room-charge posting: the POS must be able to look up a guest by room number or name and post the charge to the correct folio. Test with a staff meal — post it to a test room, verify it lands on the right folio in the PMS, then void it. Train outlet staff on the "post to room" button specifically; it's the one they'll get wrong under pressure.
Receipt printer & cash drawer
Connect the printer to the front-desk workstation (USB) or network (Ethernet) per your PMS vendor's supported list. Connect the cash drawer to the printer's drawer-kick port. Print a test folio from the PMS and confirm the drawer opens on cash transactions. Keep a spare paper roll at the desk — the 11pm checkout rush is when you'll run out.
Guest Wi-Fi segmentation
Configure the guest network on its own VLAN with client isolation, firewalled off from the PMS, POS, and payment networks. Verify from a guest device that you cannot reach the PMS server, the interface service, or any terminal by IP. Re-check this after any router or access-point firmware update — updates have been known to reset VLAN settings.
6. Troubleshooting
Work the universal sequence first: power/charge → connection → what changed recently → restart network gear, then the PMS, then the terminal and peripherals.
Terminal says "not connected" but looks powered on
Check the Ethernet cable and the switch port (link lights), then confirm the payment interface service is running — the terminal can look healthy while the interface it talks to is down. Restart the interface service first, then the terminal.
Pre-authorization works but checkout settlement fails
This is usually an expired or insufficient authorization: the hold may have lapsed, or the folio total now exceeds the authorized amount. Run an incremental authorization for the difference, then settle. If it persists, the issue is between the interface service and the processor — check the network path and firewall before calling anyone.
Restaurant charge posted to the wrong room
Folio posting problems are a PMS-vendor issue first: verify the outlet POS is looking up the current room assignment (guests change rooms). Correct the folio in the PMS, and retrain on the room-lookup step — manual room-number entry is the usual culprit.
Duplicate charge after a timeout
After any timeout, verify the transaction's status before retrying — check the PMS folio and the processor's transaction list. Retrying blind is how guests get charged twice and how chargebacks start.
Night audit totals don't match the processor report
Compare the PMS day total, the outlet POS total, and the processor settlement line by line. Common causes: a settlement run before the last checkout, an incremental auth that was never completed, or a mobile-terminal batch that settled separately. Fix the process that created the gap, not just the numbers.
Who do I call for what?
Money movement, authorizations, settlement, and holds: your processor. Terminal hardware, printing, or the POS app misbehaving: your POS/terminal vendor. Folio posting, pre-auth configuration, or the payment interface: your PMS vendor first. Calling the wrong one costs you a day.
7. Hardware options reference
Real products with links to the manufacturer's own pages (verified 2026-09-28). Models change — confirm compatibility with your PMS vendor before buying.
Payment terminals
- Moneris Go terminal — Moneris's countertop smart terminal for Canadian businesses. Check Moneris's terminal overview for current models and availability: Moneris Go terminal help & product page.
- Helcim Smart Terminal — countertop smart terminal; Helcim publishes Canadian pricing on its own page (listed at CA$429 when checked 2026-09-28 — confirm current pricing before budgeting): Helcim Smart Terminal pricing (Canada).
Receipt printers
- Epson TM-T88VII — the workhorse thermal receipt printer found at countless front desks; Ethernet and USB models available: Epson Canada TM-T88VII product page.
- Star Micronics TSP143III series — compact thermal receipt printer with USB, Ethernet, Bluetooth, and Wi-Fi variants (manufacturer's regional product page): Star TSP143III product page.
Scanner and cash-drawer models vary by POS vendor — use your POS vendor's supported-hardware list rather than buying generic. For anything not listed here, your PMS vendor's compatibility list outranks any recommendation.
🔒 PCI scope: where your card data flows matters
Whether your PMS and workstations fall inside or outside your PCI compliance scope depends on one thing: does card data pass through the PMS, or does it stay inside the payment terminal? A standalone or properly semi-integrated terminal keeps card data out of your other systems; a setup where card numbers flow through the PMS pulls far more of your network into scope.
Read the plain-language PCI scope guide → (conceptual only — always check current official requirements with the PCI Security Standards Council.)
9. Integrations you may also need
Each integration below: what it is, why it matters, what it costs, and an honestly labelled illustrative ROI sketch.
Channel manager
What it is: software that pushes your rates and availability to online travel agencies (OTAs) and pulls reservations back into your PMS, keeping every channel in sync.
Benefits: no double-bookings, one place to manage rates, and less manual entry per reservation.
Cost: quote-based — typically priced per property or per room per month. Confirm current pricing with vendors.
Direct-booking shift sketch
| Item | Amount |
|---|---|
| Room-nights shifted from OTA to direct (example) | 20 / month |
| Average daily rate (example) | $180 |
| OTA commission avoided (example: 18%) | $648 / month |
Illustrative only. Your ADR, commission rates, and shift potential will differ. Shown to demonstrate the shape of the math, not a result.
Booking engine (on your website)
What it is: the reservation widget on your own site that feeds bookings straight into the PMS.
Benefits: commission-free direct bookings and guest data you actually own.
Cost: often bundled with the PMS or channel manager; standalone options are quote-based.
Guest messaging / CRM
What it is: automated pre-arrival messages, in-stay requests, and post-stay review requests tied to the PMS guest record.
Benefits: fewer front-desk interruptions, more reviews, and repeat bookings you can measure.
Cost: quote-based per property; entry tiers exist for small independents.
Revenue management
What it is: pricing tools that adjust your rates based on occupancy, seasonality, and demand signals.
Benefits: steadier occupancy and higher revenue per available room without manual rate changes.
Cost: quote-based; usually aimed at larger properties, with lighter tools emerging for independents.
ROI sketches are illustrative examples to show how the math works — not quotes, guarantees, or predictions.
10. Everything integrated — full system map
How the pieces connect when it's all working.
direct reservations→ PMS
reservations · folios · audit← Channel manager
OTA rates & availability
pre-auth · settlement↔ Countertop + mobile terminals→ Processor
moves the money
restaurant / bar / spa→ Room folio in PMS→ Night audit
PMS ↔ POS ↔ processor→ Accounting
summarized revenue
Orbiting the PMS: housekeeping (room status), maintenance (work orders), guest messaging/CRM, and revenue management (rates). Guest Wi-Fi sits entirely outside this map — isolated, as in the sample setup above.
11. What normal looks like — technology spending benchmarks
Published IT-spending figures for context. Payment processing fees sit outside these formal IT budgets — add them separately when comparing total cost.
| Property size (annual revenue) | Typical technology spend (% of revenue) | Notes |
|---|---|---|
| Under $500K | No credible exact benchmark | Small independents vary too widely; use qualitative planning, not a percentage. |
| $500K – $5M | ≈ 1–3% | Typical small-property range. |
| $5M – $50M | ≈ 2–3% | Mid-size properties and small groups. |
| $50M+ | ≈ 2–4% | Larger portfolios with more systems to run. |
A broad lodging benchmark often cited puts technology spend at under 3% of revenue (Hospitality Technology, 2022). Treat these as context for budgeting, not targets — and remember that processing fees, which can rival the whole IT budget, are not in these figures.
Wondering what you're really paying in processing? The free audit measures your true effective rate from your own statements.
12. How AI is changing this sector
Real products, honestly framed. Prices below are third-party published figures accessed 2026-09-28 and subject to change — confirm current pricing with the vendor.
- Asksuite — AI chat for hotel websites that answers guest questions and pushes toward direct booking. Pricing is typically quote-based per property; third-party listings show plans starting around $300/month.
- HiJiffy — guest-messaging AI across web chat, WhatsApp, and social channels. Pricing quoted per property; third-party listings show around $200/month.
- Myma.ai — AI guest-experience platform for messaging and upsells. Third-party listings show around $100/month.
- GuestChat — AI chat focused on capturing direct bookings. Third-party listings show around $200/month.
The honest way to evaluate any of these: measure direct-booking lift. If the tool costs $300/month and it shifts even a few room-nights a month from OTA commission to direct, it pays for itself; if it doesn't move the needle in 90 days, cancel it. AI chat is early — treat every vendor claim as a hypothesis to test on your own numbers, not a fact.
Enterprise software landscape
Large chains and portfolios run enterprise-grade property management suites with centralized reservations, revenue management, and multi-property reporting — a different market from the independent-property tools above, evaluated through analyst research rather than per-property trials. If you operate at that scale, analyst methodology such as Gartner's Magic Quadrant research methodology explains how those evaluations are constructed. For everyone else, this section can be safely ignored.
Paying too much to take cards at your front desk?
Send 3–6 months of processing statements. We'll find the overcharges — you keep half of the documented savings, and owe nothing if we find nothing.
Start your free audit