Choosing a Payment Processor That Integrates With Your Hotel PMS
Use this hotel PMS payment integration checklist to compare processors on tokenization, folio posting, holds, hidden fees and switching costs.
Photo: Pixabay
On this page 7 sections
- Why Standalone Terminals Cost Hotels Time and Money
- How Hotel PMS Payment Integration Works Behind the Scenes
- Must-Have Features: Tokenization, Auto-Posting, and Holds
- Questions to Ask About Certified PMS Credit Card Integrations
- Hidden Fees in PMS-Bundled Payment Processing
- Switching Processors Without Losing Stored Guest Cards
- Next Steps for Your Property
Key takeaways
- A certified hotel PMS payment integration posts charges to folios automatically, which cuts keying errors and makes night audit easier.
- Tokenization keeps raw card numbers out of your PMS. Ask who owns the token vault before you sign.
- PMS-bundled payments can carry layered fees and exclusivity terms. Get every cost in writing and compare it against a third-party processor.
- Switching processors means migrating stored guest cards for future reservations. Plan the token transfer before you give notice.
Your property management system (PMS) runs the front desk. Reservations, room assignments, folios and night audit all live there. When your card processor doesn't connect to it, staff end up copying amounts between screens, and errors pile up. This guide explains how hotel PMS payment integration works and which features matter most. It also covers what to ask vendors about certification, the fees that tend to hide inside bundled payment offers, and how to switch processors without losing the guest cards stored for upcoming stays.
Why Standalone Terminals Cost Hotels Time and Money
Many independent hotels, inns and motels still run cards on a terminal that has no connection to the PMS. The front desk agent swipes or dips the card, waits for an approval, then types the amount and approval code into the guest folio by hand. That works on a slow Tuesday. It breaks down during a Friday check-in rush or a full-house weekend.
Common problems with standalone setups:
- Double entry. Every deposit, pre-authorization, incidental charge and checkout payment has to be entered twice, once on the terminal and once in the PMS.
- Night audit mismatches. The terminal batch and the PMS payment report rarely match on the first try. Someone has to hunt down the transposed digit or the charge that was run but never posted.
- Paper card numbers. Phone reservations often get written on notepads or typed into reservation notes. That creates real PCI DSS exposure.
- Hold management by memory. Staff have to remember to release or capture pre-authorizations. When they forget, guests call about money tied up on their cards.
- Weak dispute evidence. When a guest disputes a charge, the signed folio, the authorization record and the registration card sit in different systems.
| Task | Standalone terminal | Integrated with PMS |
|---|---|---|
| Check-in pre-authorization | Run on terminal, key into folio | Started from the PMS, recorded on the folio automatically |
| Incidental charges | Manual posting | Posted to folio, adjusted at checkout |
| Phone/keyed bookings | Card number often stored in notes | Card captured and tokenized at booking |
| Night audit | Manual reconciliation | Payment totals reported from the same data |
| Refunds | Look up original transaction separately | Issued against the original folio payment |
Illustrative example: a small roadside property with one agent on overnight shift might spend a noticeable part of each audit matching terminal receipts to folios. With an integration, that agent reviews a payment report instead of rebuilding it.
How Hotel PMS Payment Integration Works Behind the Scenes
An integration is a software connection between your PMS and a payment gateway or processor. When an agent clicks "authorize" or "check out" in the PMS, the PMS sends the request to the payment side and gets a result back. The approval, the amount and a token then post to the folio.
There are two main designs:
Semi-Integrated
The card terminal or PIN pad at the front desk talks directly to the processor. The PMS sends the amount to the device, the guest taps, dips or swipes, and the PMS receives only the result and a token. Raw card data never touches the PMS. For most properties this design shrinks PCI DSS scope, because the system your staff use every day doesn't store or transmit full card numbers. For more on reducing that scope across your operation, see our guide to PCI compliance for hotels and why to stop taking card numbers by email.
Fully Integrated (Gateway-Based)
The PMS sends transactions through a payment gateway. This is common for online booking engine payments, keyed phone reservations and charges against a card on file. Card entry usually happens in a secure hosted field or payment page rather than a field inside the PMS itself. Most modern hotels use both: a gateway for card-not-present charges and semi-integrated devices for guests standing at the desk.
Whichever design you use, the integration should cover every channel where you take payment:
- In person: check-in pre-authorizations and checkout settlement on EMV-capable devices
- Online: deposits and prepayments from your booking engine
- Keyed: phone reservations, group contracts and card-not-present charges for guaranteed bookings
- Outlets: restaurant, bar, spa or gift shop charges posted to the room, if those outlets run their own POS
Must-Have Features: Tokenization, Auto-Posting, and Holds
Integrations vary widely in what they actually do. These are the features that matter most for lodging.
Tokenization in the Hotel PMS
Tokenization replaces the card number with a random reference value. Your PMS stores the token, and the real card data sits in the processor's or gateway's secure vault. When you need to charge for incidentals, a no-show or a later deposit, the PMS sends the token rather than the card number. For cards that arrive from booking sites, see our guide on how to charge OTA virtual cards from Expedia and Booking.com.
Ask specifically:
- Is the card tokenized at the moment of capture, including bookings from your website and phone reservations?
- Does the integration support network tokens (issued through the card networks), processor tokens, or both? Network tokens can help a stored card keep working after the guest's card is reissued.
- How are tokens handled for cards received from online travel agencies, including virtual cards?
Automatic Folio Posting
Every authorization, capture, refund and void should post to the correct folio without anyone retyping it. Look for support for split folios, group master accounts and routing charges between folios. Corporate and wedding blocks make heavy use of these.
Pre-Authorizations, Incrementals and Holds
Lodging has its own authorization patterns. You estimate the stay at check-in, add incremental authorizations when a guest extends or runs up incidentals, and capture the final amount at checkout. Card network rules govern how these work, so your integration should handle them natively rather than through workarounds. For practical guidance, see our article on how much to authorize for incidental holds and when to release them, plus our explainer on how long credit card authorization holds last.
No-Show and Guarantee Handling
Charging a guaranteed booking that never arrived requires the right transaction type and the right records. Our guide to card network rules for hotel no-show charges explains what to capture at booking. When someone other than the guest pays for the stay, see our guide to setting up fraud-resistant hotel third-party credit card authorization forms.
Reporting That Supports Disputes
Check whether the integration lets you pull the folio, registration details and authorization history together. That bundle is the core of any response when you're winning hotel chargebacks on no-show and "didn't stay" claims. For fees added after a guest leaves, see our guide to charging guests for damage and smoking after checkout.
Questions to Ask About Certified PMS Credit Card Integrations
"We integrate with your PMS" can mean anything from a fully certified, actively maintained connection to a CSV export. Use this checklist when comparing candidates for the best payment processor for hotels like yours:
- Is the integration certified by my PMS vendor, and for which version? Certification lists are often tied to specific PMS releases and devices.
- Which terminals or PIN pads are certified? A device can be EMV-ready and still not work with your PMS. Get the exact model names.
- Who builds and maintains the connection? It could be the PMS vendor, the gateway or a third-party middleware company. Ask who fixes it when a PMS update breaks payments.
- Which transaction types are supported? Confirm pre-authorization, incremental authorization, capture, partial reversal, refund, void and card-on-file charges.
- Does it cover the booking engine and channel manager, or only the front desk?
- Who handles support at 2 a.m.? Night audit problems don't wait for business hours. Find out whether the PMS vendor or the processor answers first, and how fast.
- Who owns the token vault? This is the single most important question for future switching (see below).
- Can you show me how the integration handles a cost program? If you plan to use surcharging where permitted or dual pricing, the folio has to display the charges correctly and consistently.
Request a live demo inside a test version of your PMS, not a slide deck. Watch a full guest cycle: booking, check-in authorization, an incidental posting, an extension, checkout and a refund.
Hidden Fees in PMS-Bundled Payment Processing
Many PMS vendors now offer their own payments module or require a preferred processor. Bundled property management system payment processing can be convenient. But the pricing often has more layers than a standalone processing quote, so read the whole agreement.
Costs to ask about, in writing:
- Payment module or integration fees charged by the PMS vendor, monthly or per property
- Gateway fees, per transaction or per month, on top of processing
- Device rental or certification fees for front desk terminals
- Revenue sharing, where the processor pays the PMS vendor a cut that may be built into your rates
- Higher pricing tiers or penalties if you choose an outside processor instead of the bundled one
- PCI compliance or non-compliance fees
- Chargeback and retrieval fees
- Contract length, auto-renewal and early termination terms, including whether the payment and PMS contracts are linked so you can't leave one without the other
Pricing structure matters as much as the headline rate. Ask for a sample statement showing how a typical month of check-ins, deposits and keyed bookings would be billed. If you have current statements, have a provider review them so you can compare like for like. Exact rates and fees vary by provider and change over time, so confirm current terms before you sign.
Switching Processors Without Losing Stored Guest Cards
This is the switching cost vendors rarely bring up. A hotel can hold months of future reservations, each guaranteed with a tokenized card. Tokens issued by one processor or gateway generally can't be used by another. If you switch without a plan, those future bookings can lose their guarantees overnight.
Plan the Migration Before You Give Notice
- Read your contract for data portability terms. Some agreements address whether and how card data can be transferred to a new provider.
- Ask your new provider whether they accept PCI-compliant token migrations and what format they need.
- Request the transfer from your current provider. This should be a secure, encrypted transfer of card data directly between compliant vaults, never a spreadsheet emailed to the front desk.
- Map old tokens to new tokens in the PMS. Confirm who does this mapping and how it will be tested.
- Run both processors in parallel for a period. Settle existing pre-authorizations and in-house guests on the old processor while new bookings flow to the new one.
- Have a fallback for cards that don't migrate. Plan how you'll contact affected guests for a new card and record their consent appropriately.
Choose Portability up Front
Your next switch gets easier if you pick today's processor with exit in mind. Prefer setups where the token vault sits with a gateway you can keep even if you change acquirers, or where the contract commits to migrating your data on request. Gateways such as Authorize.Net and NMI are common in multi-channel setups. Whether either fits depends on what your PMS supports.
Never ask staff to copy card numbers out of the old system to "re-enter later." It creates serious PCI DSS risk and may breach your agreements and card network rules.
Next Steps for Your Property
Start with an inventory: your PMS and version, your booking engine, your front desk devices, and every place a card enters your operation. Then use the checklist above to compare at least two options, including any bundled offer from your PMS vendor. If you're also considering unattended check-in, see our guide to hotel self check-in kiosk costs, payments and guest fraud risks.
MannyPay offers payment processing for hotels, along with payment gateways, PIN pads for the front desk, and cost programs such as cash discount, dual pricing and surcharging where permitted. Which integration paths and devices fit your property depends on your PMS, so bring your PMS details and recent statements to the conversation. When you request a free quote, a MannyPay specialist responds within one business day.
This article is general information, not legal or compliance advice. Confirm PCI DSS obligations, card network rules and contract terms with your providers and a qualified professional.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
