A payment gateway is the technology that securely processes a guest’s card, UPI, net banking, or wallet payment when they pay for a hotel or homestay booking online, moving money from the guest’s bank to the property’s account without either side handling sensitive payment details directly. It sits quietly behind the booking button, but almost nothing about online payments works without it.
For a property owner in India, choosing and configuring a payment gateway is not just a technical checkbox. It affects how quickly guests trust the booking process, how much of each transaction is lost to fees, how fast money actually reaches the bank account, and how well the property is protected against fraud and disputed charges.
This page explains what a payment gateway does in plain terms, why the choice matters more for small and independent properties than most owners realise, and how to set one up correctly without losing revenue to avoidable mistakes.
Table of Contents
What a Payment Gateway Actually Is
At its core, a payment gateway is a piece of software that connects a booking website or engine to the banking network. When a guest enters card details or chooses UPI at checkout, the gateway encrypts that information, sends it to the card network or bank for approval, and returns a simple accepted or declined response within seconds.
The gateway itself never holds the money. It is more like a secure messenger between the guest’s bank, the card network, and the property’s bank account, with a payment aggregator or acquiring bank actually settling the funds. Property owners sometimes assume the gateway holds their money, which leads to confusion when payouts take a day or two to arrive.
In India, common payment gateway providers integrated with hotel and homestay booking engines include Razorpay, PayU, CCAvenue, and Cashfree, each supporting cards, UPI, net banking, and popular wallets. Most property management systems and booking engines, including OpenStays, connect to one or more of these providers so a guest can pay directly at the time of booking.
A payment gateway is different from a payment aggregator, though the two terms are often used loosely in conversation. The gateway handles the technical transaction and security layer, while the aggregator is the entity that holds a merchant account on the property’s behalf and settles funds into the property’s bank account, sometimes after deducting its commission.
It is also different from a point of sale machine, which is the physical card swipe device used at a front desk for in-person payments. A payment gateway works only for online and remote transactions, such as a guest paying while booking through a website, while a POS machine handles the guest physically present at check-in or check-out.
Every payment gateway transaction generates a unique transaction ID, which becomes important for reconciliation, refunds, and resolving any dispute a guest might raise later. Property owners who do not keep track of these IDs against their booking records often struggle when a guest claims a payment failed but the amount was actually deducted.
Setting up a gateway typically requires basic business documents such as PAN, GST registration where applicable, a cancelled cheque or bank account proof, and a description of the property’s business. Most providers complete this verification, sometimes called onboarding or KYC, within a few working days for a straightforward small property.
Recurring or scheduled payments, such as charging a security deposit automatically a set number of days before check-in, are another feature some gateways support natively. This removes the need for a property to manually follow up with guests for a second payment, which is especially useful for longer stays or higher value bookings where a deposit and a balance are collected separately.
Chargebacks are a related concept property owners should understand before they run into one. A chargeback happens when a guest disputes a charge with their bank directly, rather than requesting a refund from the property, and the funds can be pulled back even after settlement. Keeping clear records of booking confirmations and guest communication helps a property respond to a chargeback with evidence if one arises.
It is worth noting that a payment gateway is not the same as the booking engine itself, even though guests experience them as one seamless flow. The booking engine manages availability, rates, and the reservation record, while the gateway strictly handles moving money, and a property typically needs both working together rather than treating either as a substitute for the other.
Why Payment Gateways Matter for Indian Hotels and Homestays
For Indian hotels and homestays, a working payment gateway is often the difference between a guest who completes a booking and one who abandons it midway. Guests browsing on a phone expect to pay in the same flow, without being redirected to call the property or transfer money manually through a separate banking app.
UPI in particular has become the dominant payment method for domestic travellers, and a gateway that supports UPI smoothly, including scan and pay options, can noticeably increase the share of guests who complete payment at the time of booking rather than leaving with only a tentative reservation.
Advance payments and deposits, which many small properties rely on to reduce no-shows, are only practical when a gateway is in place. Asking a guest to complete a bank transfer manually adds friction and delay, and a meaningful share of guests simply never finish the process, resulting in a lost booking that looked confirmed on paper.
A reliable gateway also protects the property from a category of fraud that has become common on Indian OTAs and direct booking channels, where a guest uses a stolen card to make a reservation. A properly configured gateway with fraud checks in place declines many of these attempts automatically, before the property ever finds out about them.
Settlement speed is another practical concern for small operators who run on tight cash flow. Some gateways settle funds within twenty four hours, while others take two to three working days, and this difference genuinely affects a homestay owner’s ability to pay staff or suppliers on time during a busy season.
Guests are also more cautious than they once were about where they enter card details. A property that routes payment through a well known, secure gateway, rather than asking for card numbers over WhatsApp or email, comes across as more professional and trustworthy, which matters especially for newer or lesser known homestays trying to build a reputation.
Seasonal cash flow is a real constraint for many homestays and small hotels, particularly those that see the bulk of their bookings concentrated in a few months of the year. A gateway with fast, predictable settlement means a property can plan staffing, maintenance, and supply purchases with more confidence, rather than waiting on delayed or unpredictable payouts during the busiest weeks.
There is also a compliance angle. Properties above certain turnover thresholds are required to maintain proper digital transaction records for tax purposes, and a payment gateway automatically generates this trail, which is far more reliable than trying to reconstruct it from bank statements and manual notes at the end of the financial year.
Guest experience research consistently shows that a confusing or untrustworthy checkout is one of the biggest reasons a traveller abandons a booking at the last step, even after browsing rooms and comparing rates carefully. For an independent property competing against large OTAs with polished checkout flows, matching that same level of payment reliability is one of the more affordable ways to close the gap.
Finally, a working gateway makes it far easier to run promotions and early-bird offers with any confidence, since the property can require full or partial payment at the time of booking to lock in the discounted rate, rather than relying on a guest’s word that they will pay closer to arrival.
How a Payment Gateway Transaction Flows, Step by Step
The basic payment gateway flow is largely the same across providers, even though the interface and settlement timelines differ. Understanding each step helps a property owner troubleshoot when a guest reports a payment issue.
- Guest selects dates and room, then proceeds to the payment step on the booking engine or website.
- Guest chooses a payment method, such as card, UPI, net banking, or wallet, and enters the required details.
- The payment gateway encrypts the details and sends an authorisation request to the guest’s bank or UPI app.
- The bank or UPI app approves or declines the transaction, often with a one-time password or biometric confirmation.
- The gateway returns the result to the booking engine within seconds, and the booking is confirmed if approved.
- The aggregator settles the funds into the property’s bank account, typically within one to three working days, minus the gateway’s transaction fee.
Payment Gateway vs UPI vs POS vs Cash
| Method | Where It’s Used | Speed to Property | Guest Effort |
|---|---|---|---|
| Payment Gateway | Online booking checkout | 1 to 3 working days | Low, done during booking |
| UPI Direct (Manual) | Guest sends via UPI app outside checkout | Instant to property, but unverified | Medium, needs manual confirmation |
| POS Machine | In-person at check-in or check-out | 1 to 2 working days | Low, but requires physical presence |
| Cash | In-person at the property | Immediate | None, but no digital record |
What a Good Payment Gateway Setup Should Include
- Support for UPI, major cards, net banking, and popular wallets, since guests differ widely in payment preference.
- Fraud and risk checks built into the gateway, so suspicious transactions are flagged or declined automatically.
- Clear, itemised settlement reports so every payout can be matched against specific bookings.
- A transparent fee structure, ideally a flat percentage with no hidden charges for refunds or chargebacks.
- Mobile-friendly checkout, since a large share of Indian travellers book and pay from a phone.
- Automatic booking confirmation the moment payment succeeds, without manual intervention from the property.
- A working refund process that the gateway can process directly, rather than requiring a separate manual transfer.
- Integration with the property’s booking engine or PMS, so payment status updates the reservation automatically.
- Multi-currency support if the property expects a meaningful share of international guests.
- Responsive customer support from the gateway provider for when a transaction dispute needs quick resolution.
- Clear, guest-facing payment confirmation pages and email or SMS receipts sent automatically after a successful transaction.
- Support for partial payments or deposits, so a property can collect an advance now and the balance closer to check-in.
Common Mistakes Property Owners Make With Payment Gateways
Asking guests to share card details over WhatsApp or email. This is both a security risk and a red flag to guests who increasingly recognise it as an unsafe practice, and it can expose the property to liability if the details are misused.
Not checking settlement timelines before signing up. Some gateways advertise attractive fees but settle funds slowly, which can strain cash flow for a small property that needs quick access to booking revenue.
Ignoring the fee structure until the first invoice arrives. Transaction fees, refund charges, and chargeback fees can add up meaningfully over a season, and comparing providers only on headline rates often hides the real cost.
Not reconciling settlement reports against bookings regularly. Skipping reconciliation makes it hard to catch a missed payout or a duplicate charge until a guest complains, by which point the fix is more time consuming.
Using a gateway that does not support UPI properly. Since UPI is the preferred method for a large share of Indian travellers, a clunky or missing UPI flow at checkout directly costs bookings.
Leaving refunds to be processed manually. A manual refund process is slower for the guest and creates more room for error than letting the gateway handle it directly against the original transaction.
Not testing the payment flow from a guest’s perspective. Owners who never attempt a real booking themselves often miss friction points, broken redirects, or confusing steps that quietly reduce completed bookings.
Not having a backup gateway or payment method. If a single gateway goes down, even briefly, a property with no alternative payment option risks losing bookings during the outage, which is why some larger properties keep a second provider or a manual UPI QR code as a fallback.
Setting Up a Payment Gateway Correctly
Follow these steps to set up a payment gateway correctly for a hotel or homestay in India.
1. Choose a gateway provider suited to small properties
Compare two or three providers commonly used by Indian hotels and homestays on fees, settlement speed, and UPI support before committing.
2. Complete business verification and KYC
Submit PAN, GST details where applicable, and bank account proof so the provider can verify the business and activate the account.
3. Connect the gateway to the booking engine or PMS
Use the provider’s plugin or API integration, or work with the booking engine’s support team, so payments update reservations automatically.
4. Test the checkout flow end to end
Make a small real booking as a guest would, using different payment methods, to confirm confirmations and receipts work correctly.
5. Set up settlement and reconciliation habits
Check payout reports weekly against the booking calendar so any mismatch is caught early rather than discovered much later.
6. Review fees and performance periodically
Revisit the gateway’s fees and reliability every few months, since better rates or features may become available as the property grows.
Payment Gateway Checklist
- Does the gateway support UPI, cards, net banking, and wallets smoothly?
- Are settlement timelines clear and acceptable for the property’s cash flow needs?
- Is the full fee structure, including refund and chargeback charges, understood?
- Is the checkout flow mobile-friendly and tested from a guest’s perspective?
- Does the gateway integrate directly with the booking engine or PMS?
- Are fraud and risk checks active and appropriately configured?
- Is there a working, gateway-handled refund process rather than a manual one?
- Are settlement reports being reconciled against bookings on a regular schedule?
- Has KYC and business verification been fully completed with no pending steps?
- Is customer support from the provider responsive when a dispute needs resolving?
- Is there a documented process for handling a chargeback or payment dispute if one arises?
- Does the property have a backup payment method in case the primary gateway has an outage?
Payment Gateway in Action: A Short Example
Deepika runs a small heritage guesthouse in Pondicherry with six rooms, most of them booked directly through her website rather than an OTA. Before she set up a proper payment gateway, guests would confirm a booking and then be asked to transfer an advance manually, and a noticeable share simply never completed the transfer, leaving her with unconfirmed dates she could not confidently hold or release.
Once we added a proper gateway with UPI at checkout, the number of guests who actually paid at the time of booking went up a lot. We also stopped worrying about someone claiming they had paid when they had not, because everything is logged with a transaction ID now.
Deepika, Heritage Guesthouse Owner, Pondicherry
Frequently Asked Questions
Is a payment gateway the same as a payment aggregator?
Not exactly. The gateway handles the technical transaction and security layer, while the aggregator holds the merchant account and settles funds into the property’s bank account, though many providers offer both functions together.
How long does it take for payment gateway funds to reach the property’s bank account?
Most providers settle within one to three working days, though some offer faster next-day settlement, often for a slightly higher fee.
Do payment gateways charge a fee on every transaction?
Yes, almost all gateways charge a percentage-based transaction fee, typically in the range of one and a half to three percent, though the exact rate depends on the provider and payment method.
Can a small homestay with only a few rooms use a payment gateway?
Yes. Most Indian gateway providers support businesses of any size, and many booking engines used by small properties, including OpenStays, offer built-in gateway integration.
What happens if a guest’s payment fails during checkout?
The gateway simply declines the transaction and the guest is shown an error, usually with an option to retry with a different payment method. No booking is confirmed unless payment succeeds.
Is UPI processed through the same payment gateway as card payments?
Yes, most Indian gateways handle UPI, cards, net banking, and wallets through the same integration, so the property does not need separate setups for each method.
What documents are typically needed to set up a payment gateway?
Common requirements include PAN, GST registration where applicable, a cancelled cheque or bank account proof, and basic business details, though exact requirements vary by provider.
What is a chargeback and how is it different from a refund?
A refund is initiated by the property, typically at the guest’s request, while a chargeback is initiated by the guest’s bank after a dispute, and funds can be reversed even after the property has already received the payout.
Can a property use more than one payment gateway at the same time?
Yes, and some larger properties do this deliberately, either to offer guests more payment options or to have a fallback in case one provider has downtime or processing issues.
Choosing and configuring the right payment gateway is one of those decisions that quietly shapes how many bookings a property actually converts. Pair it with a clear rate plan and a consistent approach to reservations, and payments stop being a source of friction or lost revenue. If you are setting up a new property on OpenStays, our resources page has more guides on getting bookings and payments working smoothly together.