Your built-in hotel payment gateway
Collect payments, charge OTA virtual cards, and automate hotel payment workflows directly from your PMS. SabeePay keeps every transaction linked to the right guest, reservation, and folio.
The Challenge
Staff retype card numbers from OTA extranets, phone bookings, or email requests — a slow process that creates PCI risk every time a card number is written down or copied between systems.
OTA virtual cards from Booking.com, Expedia, and other channels have to be located, matched to the right reservation, and charged individually — unless your gateway can do it in bulk.
When payments run through a separate system, your team manually matches transactions back to reservations and folios, and your revenue reporting lags behind the front desk.
What SabeePay does
0.5% per transaction — no separate SabeePay subscription.




Also: bank transfer & pay on arrival
Rate policy: 30% deposit
01. Deposits & Balances
Set deposit, preauthorisation, and balance rules once in your rate policy, and SabeePay applies them to every reservation that uses it — from your PMS, Booking Engine, or a channel-managed OTA.
Booking Engine payment received
02. No Manual Entry
Payments from Booking Engine or Channel Manager bookings arrive already linked to the right reservation, so staff aren’t retyping card details from a confirmation email or OTA extranet.
New VCC · Booking.com
03. OTA Virtual Cards
SabeePay recognises OTA virtual cards (VCCs) from Booking.com, Expedia, and other channels as soon as the reservation lands in your PMS — no manual lookup required.
3 virtual cards selected
04. Bulk Charging
Charge multiple OTA virtual cards in one click instead of opening each extranet individually. A task that once took a chunk of a front desk shift now takes minutes.
Balance due in 3 days
05. Payment Reminders
Guests get a payment request by email when a balance is due, timed to the rate policy on their reservation — so your team isn’t chasing payments manually before arrival.
Guest tap to pay
06. One-Click Payments
Guests pay a deposit or balance online in one click. Front desk staff charge a stored card straight from the reservation screen — no separate card terminal.
How SabeePay works
Every payment already knows which reservation and folio it belongs to, so the whole flow runs without manual tracking or reconciliation.
BOOK A DEMOWhen a booking arrives, SabeePay knows what payment is required based on your rate policy. Deposits, pre-authorisations, and balance payments are ready to be managed.
SabeePay processes eligible payments, charges OTA virtual cards, or sends payment requests to guests based on your settings. Your team doesn’t need to track each payment step manually.
Once a payment completes, the transaction is added to the reservation and guest folio. Reports stay accurate, balances stay up to date, and your team avoids manual reconciliation.
See it in action
The SabeePay transaction screen shows OTA virtual cards ready to charge in bulk, payments posted straight to the guest folio, and refunds posting back to the same folio — with nothing to reconcile by hand.
BOOK A DEMOSecurity & compliance
SabeePay uses Stripe’s PCI DSS Level 1 certified infrastructure to process card payments securely, with PSD2 Strong Customer Authentication (SCA) and 3D Secure built into the payment flow. Sensitive card data is never stored in your PMS — so guest data stays protected while your team manages payments efficiently from SabeeApp.

PCI DSS Level 1 certified infrastructure
Strong Customer Authentication in the flow
Raw card numbers never stored in your PMS
Multi-currency, no extra infrastructure
Works together with
SabeePay is part of the SabeeApp ecosystem, so payments flow between products automatically — no exports, no re-keying.
Every payment posts straight to the right reservation folio.
Explore PMS →Guests pay for direct bookings without leaving the checkout flow.
Explore Booking Engine →OTA virtual cards arrive matched to the reservation that generated them.
Explore Channel Manager →Guests pay for online check-in extras and outstanding balances from their phone.
Explore Smart Solutions →Simple, transparent pricing
SabeePay is available to every SabeeApp customer and activated separately. There’s no monthly subscription for SabeePay itself — just 0.5% per successful transaction on top of Stripe’s standard processing fees.
SEE FULL PRICINGSabeePay transaction fee
No monthly subscription for SabeePay itself
Also available · Collect card details for manual charging, or offer bank transfer, PayPal & pay on arrival
Compare
Trusted by 6,000+ hoteliers in 70+ countries.
Trusted by 6,000+ hoteliers in 70+ countries
Every hotel manages payments differently. Talk with our hospitality experts and find the right setup for your payment workflows.
FAQ
SabeePay is SabeeApp’s built-in hotel payment gateway. It processes card payments, digital wallets, and OTA virtual cards, and transfers every transaction securely to the right reservation folio in your PMS — with full PCI DSS and PSD2/SCA compliance.
Both. SabeePay initiates the charge, runs it through PCI DSS and PSD2 compliant processing via Stripe, and posts the result to the guest folio without a separate entry from your team. You don’t need a separate payment processor alongside SabeeApp.
SabeePay is available to every SabeeApp customer but activated separately. It’s charged at 0.5% per successful transaction on top of Stripe’s standard processing fees, with no extra monthly subscription cost for SabeePay itself.
Cards (Visa, Mastercard, Maestro), OTA virtual credit cards, Apple Pay, Google Pay, SEPA, PayPal, bank transfer, and payment on arrival — across multiple currencies.
Yes. PCI DSS compliance is handled through Stripe at Level 1, and PSD2’s Strong Customer Authentication requirements are built into the checkout flow, which also helps reduce chargebacks.
It detects OTA virtual cards as soon as they arrive, lets you charge several in one click, times payment reminders to the rate policy so your team isn’t chasing guests manually, and posts every transaction to the folio without manual entry.
Yes. Every payment, refund, and pending balance updates the guest folio and your financial reports in real time.
Yes. This is useful for small hotel groups or owners managing several properties under one company entity.
Yes. SabeePay can generate a payment request based on the rate policy attached to the reservation, without your team creating it manually each time.
No. Payments settle to your Stripe merchant account first, then transfer to your bank account on Stripe’s standard payout schedule.
SabeeApp doesn’t support external payment gateways. Alongside SabeePay, you can still collect card details for manual charging, or offer bank transfer, PayPal, or payment on arrival.
Your front desk receives an alert, and Stripe manages the dispute and chargeback process on SabeePay’s behalf.
Technically yes, but PSD2’s Strong Customer Authentication may require the guest to re-authenticate the charge, so it isn’t always as instant as an in-stay charge.
SabeePay does not store raw card numbers in your PMS. Card details are securely tokenised through Stripe, allowing authorised payments to be processed without your team accessing sensitive card information.