A hotel booking payment gateway should support the whole reservation lifecycle: the amount collected today, the balance due later, and the refund or release if plans change. A deposit is a captured payment; a pre-authorisation temporarily holds funds on the guest’s card. They create different obligations and cash-flow effects. Adyen’s hospitality example illustrates how an eligible pre-authorisation can be adjusted before the final amount is captured.
For US and Canadian hotel merchants serving US cardholders, the useful comparison is how the provider fits your legal entity, booking system, charge timing and settlement needs. Our travel and hospitality payment solutions overview covers the wider provider-selection task. This guide focuses on the operational decisions behind a hotel reservation.
What a hotel booking payment gateway must connect
Start with a responsibility map. The booking engine creates the reservation, the property management system (PMS) manages the stay, the gateway handles the payment request, and the acquiring provider reviews and processes the merchant’s transactions. A booking reference is not necessarily a payment reference. Decide which system owns each status and how staff see failed or incomplete actions.
Map direct reservations separately from online travel agency bookings. For each channel, establish who is merchant of record, who receives the guest’s money, and whether the hotel receives a payment, a remittance or an agency-issued virtual card. Do not send the same reservation through two collection paths simply because it appears in both systems.
Deposit, pre-authorisation or full payment?
| Arrangement | What happens | Operational check |
|---|---|---|
| Captured deposit | The agreed amount is charged before the stay. | Record the refundable and non-refundable conditions and the remaining balance. |
| Pre-authorisation | The issuer holds an amount without the merchant capturing it yet. | Track the actual expiry and supported adjustment or capture process. |
| Full prepayment | The booking amount is collected in advance. | Match refund exposure and supplier obligations to the payout terms. |
| Payment near arrival | A later payment is requested under the agreed booking terms. | Provide a recovery path if the saved credential or payment request fails. |
A hold placed when a guest books months ahead should not be assumed to remain valid until arrival. Authorisation windows and extensions depend on the payment method, transaction type and provider. Stripe’s authorisation-and-capture documentation explains that uncaptured authorisations expire and release the funds. Ask the provider which dates and statuses the PMS must track.
A booking-to-settlement example
Consider an illustrative US$1,000 direct booking with a US$200 deposit and US$800 remaining balance. If the deposit is captured, show US$200 paid and US$800 due on the reservation. A separate US$150 incidental authorisation near check-in is a hold, not another US$150 of collected revenue.
At checkout, staff should see the amount already paid, any agreed additional charges, the capture outcome and the unused hold to release. Finance then reconciles the captured transactions to the provider’s fees, refunds, reserve movements and bank payout. These figures illustrate bookkeeping relationships; they are not a recommended deposit policy or a provider offer.
US and Canadian hotels taking US-issued cards
Keep four facts separate when requesting terms: the hotel’s legal-entity country, the acquiring arrangement, the currency shown to the guest and the currency paid to the bank account. A Canadian business accepting a US-issued card does not automatically receive domestic US acquiring or USD settlement.
Ask the shortlisted provider to confirm eligibility for your exact entity and lodging model, accepted card types, presentment and settlement currencies, conversion costs, payout deductions and any reserve. Compare the total workflow rather than a headline processing rate. Where US cards are being declined, use our guide to cross-border US-card declines to separate issuer responses, authentication and acquiring fit before changing the entire checkout.
Hotel payment gateway checks before integration
- Compatibility: ask the booking-engine or PMS vendor which specific connector, software version and payment actions are supported.
- Status handling: confirm how successful, failed and pending captures or refunds reach the reservation record.
- Saved credentials: agree how consent and provider tokens support eligible later charges. A stored token is not permission for any charge.
- Access: separate front-desk actions from finance approvals and retain an audit trail.
- Recovery: test declined payments, duplicate requests, expired holds and cancellations in the provider’s test environment.
A payment logo on another hotel’s website is a useful research clue, but it does not establish approval for your property or compatibility with your PMS. Check the vendor’s integration documentation and obtain confirmation from the provider before commissioning development.
Refunds, no-shows and late charges
Give staff a decision rule based on the payment’s actual state. An uncaptured authorisation can require cancellation or release; a captured payment requires a refund. Adyen distinguishes these actions and notes that a refund request can subsequently fail. Reconcile the final outcome rather than treating a button click as completed repayment.
For no-shows and additional charges, document what the guest agreed to, when staff may charge, and which transaction process the provider permits. Review disputed cases with the provider using the reservation confirmation and communications. Do not promise that a non-refundable label prevents every dispute.
Keep card data out of staff notes and ordinary email. PCI SSC states that merchants must not retain card verification codes after authorisation, even with customer permission. Use the provider’s approved credential-handling process; see the PCI SSC clarification.
Hotel booking payment reconciliation
A useful daily report joins reservation ID, payment reference, captured amount, refunds, fees, reserve changes, payout ID and bank credit. Keep authorisations outside the collected-revenue total. Separate a guest refund from the provider’s reserve release: they change different balances.
For agency channels, record the contract and payment route alongside the booking. For direct bookings, investigate a mismatch at transaction level before adjusting the reservation total. Assign an owner to unresolved exceptions so a failed refund or duplicate deposit is not carried into the next reporting period.
Hotel booking payment gateway FAQ
Can a hold cover a reservation booked months ahead?
Do not assume it can. Ask which authorisation window applies and whether the provider supports the required extension. A captured deposit or a later payment request may be a different operational choice, subject to the booking terms.
Does an online travel agency collect every reservation?
Check the channel’s contract and the individual booking. Identify the collecting party, any virtual-card instructions, the hotel amount due and the party responsible for refunds before staff collect again.
What should a Canadian hotel check for US card payers?
Confirm Canadian-entity eligibility, supported US-issued cards, USD or CAD pricing, settlement-account requirements and the full cost of currency conversion and payouts. The payer’s country alone does not determine those terms.
Compare hotel payment solutions with WiseAlt
Bring your reservation channels, PMS details, average booking value, advance-booking period, refund pattern and entity information to a provider comparison. WiseAlt helps merchants compare independent providers and coordinate onboarding; integrations, approval and commercial terms remain subject to the relevant vendors and providers. Contact WiseAlt to discuss your hotel booking payment gateway requirements.
