Why Hotels Need More Than One Payment Gateway
Why a single payment gateway loses bookings, how to compare options, and how to match payments to your deposit and cancellation policies.
Jupiter Team 4 min read
A guest who cannot pay is a lost booking. Online payment is where many hotel bookings end, and the cause is often simple: the guest's card, wallet or country is not supported by the one gateway the hotel uses.
This guide explains why more than one payment option matters and how to choose them.
What a payment gateway does
A payment gateway is the secure link between your booking engine, front desk or restaurant and the payment processor. It sends the payment details to the processor, returns an approval or a decline, and keeps card data off your own systems. Your hotel does not store card numbers when payments go through a gateway.
Why one gateway is rarely enough
Hotels sell to guests from many places, and payment habits vary:
- Card brands and wallets. Some guests pay with a major credit card, others with a debit card or a digital wallet.
- Local processors. A gateway may work very well in one country and not at all in another. Canadian hotels often prefer a processor with strong local support, while others need a gateway that accepts international cards.
- Fees. Processing fees differ by gateway, card type and region. Having a choice lets you compare them.
- Reliability. If one gateway has an outage or declines a valid card, a second option saves the booking.
- Existing relationships. Many hotels already have a merchant account and would like to keep it.
Questions to ask before you choose
- Which guests do we serve, and how do they pay? Look at your last 100 bookings.
- What are the total fees? Include transaction fees, monthly fees and fees for refunds or chargebacks.
- How fast do we get the money? Settlement times vary.
- Does it work with our booking engine and PMS? Payments should be recorded on the guest folio automatically.
- How are refunds and deposits handled? Your cancellation policy should match what the gateway can do.
- Is it secure? Choose a gateway that is PCI-compliant and uses tokenization.
Match payments to your policies
The gateway is only half the picture. Decide what you charge and when:
- A deposit at booking, with the balance at check-in
- Full prepayment for non-refundable rates
- A card held as a guarantee, with no charge until arrival
- A clear no-show and cancellation policy, shown before the guest pays
Show the policy next to the payment button so guests know what to expect.
Payments beyond the booking engine
Payments happen at several points in a stay: online at booking, at the front desk at check-in and check-out, and in the restaurant or bar. If these are all recorded against the guest folio, the night audit and your accounts stay consistent.
Plan for refunds, failed payments and chargebacks
Taking payment is the easy part. What happens afterwards is where hotels lose time and money.
- Refunds. Decide who can issue a refund, how it is recorded on the folio and how long it takes to reach the guest. Refund to the original payment method wherever possible.
- Failed payments. Cards are declined for many reasons, such as insufficient funds, expired cards or bank security checks. Show a clear message and let the guest try another method straight away, so the booking is not lost.
- Chargebacks. A guest can dispute a charge with their bank. Keep records that help you respond: the booking confirmation, the cancellation policy the guest accepted, the check-in details and any messages. Clear policies shown before payment make disputes easier to resolve.
- Currency. If you accept guests from other countries, check how your gateway handles currency and what the guest sees at the point of payment.
Reconcile payments regularly. Compare the gateway's settlement reports with your folio postings so differences are caught within days, not months.
Review your gateway and fees at least once a year. Volumes, card mix and pricing change, and a gateway that suited a 20-room inn may not suit a growing group. Ask for a clear fee schedule in writing, and compare it with your actual statements.
Keep card data out of your systems
A reputable gateway handles the card details for you, using hosted fields or tokens, so card numbers never pass through your own servers. This greatly reduces your security and compliance burden. Whatever you choose, never ask guests to email card numbers, and train your staff to avoid writing them down.
Gateways Jupiter supports
Jupiter Booking Engine takes secure online payments through Stripe, Razorpay, Moneris, Square, Chase, NMI, Authorize.net and PayPal. If you use another gateway, new payment integrations are available on request, free of cost. Payments are handled by the gateway, so card details never pass through the booking engine itself. You can see the full list on the Integrations page.
Book a free demo and tell us which gateway you already use.
