A chargeback happens when a guest asks their bank or card issuer to reverse a payment instead of asking the property for a refund directly. The bank pulls the money back from the hotel or homestay’s account while it investigates, and the property has to prove the charge was valid or lose both the booking amount and the room night.
This is different from a normal refund, where the guest and the property agree on the amount and the property initiates the return through its own payment gateway or front desk process. A chargeback skips that conversation entirely and goes straight to the card network, which puts the property on the back foot from the first message it receives.
This page explains what a chargeback actually involves, why Indian hotels and homestays are seeing more of them as online and card payments grow, how the dispute process plays out step by step, and what a property can do to respond well and avoid unnecessary losses.
Table of Contents
What a Chargeback Actually Means
In payment terms, a chargeback is a forced reversal initiated by the cardholder’s bank (the issuing bank), not by the merchant. When a guest sees a charge on their statement that they do not recognise, believe is wrong, or are unhappy about, they can contact their bank and dispute it instead of contacting the property.
The issuing bank then raises the dispute with the property’s bank (the acquiring bank) or the payment gateway that processed the transaction, and the disputed amount is provisionally debited from the property’s account almost immediately, often before the property even knows a dispute exists.
The property is then given a window, usually somewhere between seven and twenty one days depending on the card network and the payment gateway’s own process, to submit evidence that the charge was legitimate. If the evidence is convincing, the bank can reverse the reversal and return the funds. If it is not, or if the property misses the deadline, the chargeback stands and the money is gone for good.
Chargebacks were originally designed as consumer protection against genuine fraud, such as a stolen card being used without the owner’s knowledge. In hospitality, though, a large share of disputes come from guests who simply find it faster to dispute a charge with their bank than to ask the property for a refund, or who dispute a charge they authorised but later regretted.
Why Chargebacks Matter for Indian Hotels and Homestays
Indian hotels and homestays are taking more card and UPI payments than ever, whether through a payment gateway on their own booking engine, through an OTAs payment flow, or as an advance payment collected over the phone. Every one of those channels carries chargeback exposure the moment a card is involved, and UPI transactions, while less prone to disputes, are not entirely immune either when a guest raises a complaint through their bank.
For a small or mid sized property, even a handful of chargebacks in a month can matter. The property loses the original booking value, often loses the payment gateway’s own dispute fee on top of that regardless of the outcome, and loses the room night that could have been sold to someone else, since guest facing cancellation windows rarely map cleanly onto when a chargeback actually lands.
There is a second, quieter cost too. Payment gateways and card networks track a property’s chargeback ratio, the share of transactions that end up disputed. A property that crosses a certain threshold, commonly cited around one percent of transactions by value or volume depending on the network, can be flagged for closer monitoring, asked to pay higher fees, or in serious cases have its payment processing restricted. Keeping that ratio low is not just about individual disputes, it protects the property’s ability to keep accepting card payments at all.
None of this means a property should be afraid of accepting card payments. It means treating chargeback readiness as a normal part of running a property, the same way a fire extinguisher is kept on hand without expecting a fire every week, so that when a dispute does show up, the response is quick, calm, and backed by records that were already in place.
How the Chargeback Process Works, Step by Step
The chargeback process moves through the same broad stages regardless of card network, though exact timelines vary by payment gateway and issuing bank.
1. Guest disputes the charge
The guest contacts their card issuing bank, not the property, and says the charge is unauthorised, incorrect, or unsatisfactory in some way. The bank opens a dispute case on their behalf.
2. Funds are pulled from the property’s account
The issuing bank notifies the property’s acquiring bank or payment gateway, and the disputed amount is provisionally debited from the property’s account, often within a few days of the guest’s complaint.
3. Property is notified and given a deadline
The payment gateway or acquiring bank informs the property that a chargeback has been raised, along with a reason code and a deadline, typically seven to twenty one days, to submit supporting evidence.
4. Property submits evidence
The property gathers booking confirmations, identity records, signed policies, communication logs, and any other proof that the charge was valid and the stay took place as agreed, then submits this through the payment gateway’s dispute portal.
5. Bank or card network reviews and decides
The issuing bank reviews the evidence against the guest’s claim and either reverses the chargeback in the property’s favour or upholds it, at which point the funds stay with the guest and the case is closed.
Common Reasons Guests File Chargebacks
| Common Reason | What It Usually Means |
|---|---|
| Unauthorised transaction | Guest claims they did not make or approve the charge, sometimes genuine card fraud, sometimes a family member booking without telling the cardholder. |
| Goods or service not as described | Guest is unhappy with the room, amenities, or service and feels the stay did not match what was promised online. |
| Duplicate or incorrect amount charged | Guest was billed twice for the same booking, or the amount charged does not match what was agreed at the time of booking. |
| Cancellation or refund not processed | Guest cancelled within the property’s stated policy and expected a refund, but it was delayed or never issued through the property’s own process. |
| Credit not processed | Property agreed to a refund but the guest’s bank statement never reflected it, often because the refund was issued to a different method or delayed on the gateway’s side. |
Chargeback vs Refund
Chargebacks and refunds both end with money moving back toward the guest, but the process, the control the property has, and the cost to the property are very different.
| Refund | Chargeback | |
|---|---|---|
| Who starts it | Property, at the guest’s request or by its own policy | Guest, through their card issuing bank |
| Property’s control | Property decides the amount and timing | Property only gets to respond with evidence after the fact |
| Extra fees | Usually none beyond the gateway’s standard processing fee | Dispute fee charged by the gateway regardless of outcome, in most cases |
| Effect on reputation with bank | No effect | Counts toward the property’s chargeback ratio with the payment gateway |
| Typical resolution time | Days, entirely within the property’s process | Weeks, decided by the issuing bank or card network |
Chargebacks and OTA Bookings
Bookings that arrive through an OTA add a layer of complexity, because the party responsible for handling a dispute depends entirely on who actually processed the payment. When an OTA collects full payment upfront and pays the property later, the OTA is usually the merchant of record and manages any chargeback itself, since the guest’s card was charged by the OTA, not by the property.
When a booking is made through an OTA but payment happens at the property, whether as an advance collected through the property’s own gateway or full payment at check in, the property is the merchant of record and carries the chargeback risk directly, exactly as it would for a booking made on its own website.
It is worth checking this with each OTA a property works with, since the split varies by platform and even by booking type on the same platform. A property that assumes an OTA is always handling disputes can be caught off guard when a chargeback notice lands directly in its own payment gateway dashboard instead.
What a Strong Chargeback Response Should Include
Winning a chargeback dispute comes down to how complete and specific the evidence is. Vague statements rarely help. Banks respond to documents that clearly tie the charge to a real booking and a real stay.
- Booking confirmation showing the guest’s name, dates, room type, and the exact amount charged, timestamped and matching the disputed transaction.
- Proof of guest consent such as a signed booking form, an accepted cancellation policy, or an email or message thread where the guest agreed to the charge.
- Identity match linking the card used to the guest who stayed, for instance a front desk check in record noting the same name and the last four digits of the card.
- Communication history including any messages exchanged with the guest before, during, or after the stay, especially anything showing the guest was satisfied or raised no complaint at check out.
- Proof of service delivered such as a signed check out form, key handover record, or utility and housekeeping logs confirming the guest actually occupied the room for the dates charged.
- Policy visibility showing the cancellation and refund policy was displayed to the guest at the time of booking, whether on the booking engine, the OTA listing, or a printed form at check in.
- Proof of the guest’s actual stay such as internet or television usage logs, key card access records, or a housekeeping entry confirming the room was occupied on the disputed nights, which is especially useful when a guest claims they never checked in at all.
- A clear, factual cover note summarising the booking, the dates, the amount, and why the charge was valid, written in plain language so the reviewing bank analyst, who has no context on the property, can follow it quickly.
Common Mistakes Properties Make With Chargebacks
Most chargeback losses are not about whether the property was in the right. They are about the property failing to respond properly within the window it was given.
- Missing the response deadline. Payment gateway notifications about disputes can land in a spam folder or go unnoticed by front desk staff who are not checking that inbox. Once the window closes, the case is lost by default no matter how strong the evidence would have been.
- Submitting incomplete evidence. A booking confirmation alone is rarely enough. Banks want to see the fuller picture, including the cancellation policy the guest agreed to and any communication around the disputed stay.
- Treating every dispute as an OTA problem. When a booking came through an OTA, some properties assume the OTA will handle the chargeback. In most cases, the payment relationship is between the property’s own gateway and the guest’s bank, and the property still has to respond directly.
- Not tracking the chargeback ratio. Properties that lose several disputes without reviewing why they lost them keep repeating the same gaps in their evidence, and their ratio with the payment gateway keeps climbing.
- Confusing a chargeback with a refund request. Issuing a refund after a chargeback has already been filed does not usually stop or reverse the dispute process, and can sometimes result in the guest receiving the money twice.
- Assuming the payment gateway will fight the case automatically. The gateway forwards the dispute and submits whatever evidence the property provides, but it does not build the property’s case. A weak or empty submission almost always loses, even through a reputable gateway.
Preventing Chargebacks Before They Happen
Preventing a chargeback is almost always cheaper than fighting one. A few consistent habits at the booking and check in stage close most of the gaps that disputes exploit.
- Display the cancellation and refund policy clearly at the point of booking, not buried in a separate terms page the guest never opens.
- Send a booking confirmation immediately after payment, with the exact amount, dates, and room type spelled out.
- Match the name on the card or payment method to the guest checking in, and keep a simple record of that match.
- Get a signature, digital or physical, on the property’s policy at check in, especially for advance payments and no show charges.
- Respond to refund requests through the property’s own process quickly, so a guest never feels forced to go around the property to their bank.
- Check the payment gateway’s dispute or chargeback dashboard on a fixed schedule, not only when someone happens to notice an email.
- Keep a simple log of every dispute received, its outcome, and the reason code, so patterns become visible over time.
- Reconcile the payment gateway’s settlement report against actual bookings every week, so a mismatched or unfamiliar transaction gets noticed early rather than only when a dispute notice arrives.
- Train front desk and reservations staff to recognise a chargeback notification email from the payment gateway, since these often look like routine account alerts and get ignored if nobody knows what to look for.
Chargeback in Action: A Short Example
Ananya runs a homestay in Rishikesh with six rooms, most of them booked through her own website using a payment gateway for advance payments. One morning she noticed a debit of eleven thousand rupees from her payment gateway account with no matching booking cancellation on her side. A guest had disputed the charge with his bank, claiming he never received a confirmation for the stay.
Ananya’s booking engine had, in fact, sent a confirmation email, but it had gone to an old address the guest had mistyped. She had eighteen days left to respond. She pulled the booking record, the payment gateway’s transaction log showing the correct card was used, and the guest’s own WhatsApp messages confirming his arrival time on the day of check in, and submitted all three through the gateway’s dispute portal.
The bank ruled in her favour twelve days later and the funds were returned. Ananya now keeps a simple rule at her homestay: no advance payment is accepted without a manual WhatsApp confirmation to the guest as a backup to the automated email, specifically to avoid this exact situation happening again.
Frequently Asked Questions
What is the difference between a chargeback and a refund?
A refund is initiated by the property, usually at the guest’s request, and the property controls the amount and timing. A chargeback is initiated by the guest through their card issuing bank, skips the property’s own refund process, and pulls the funds back before the property gets a chance to respond, leaving the property to prove the charge was valid after the fact.
How long does a property have to respond to a chargeback?
It varies by payment gateway and card network, but most disputes give the property somewhere between seven and twenty one days from the notification date to submit evidence. Missing this window usually means losing the case automatically, regardless of how strong the evidence would have been.
Can a hotel or homestay stop a guest from filing a chargeback?
No, a guest can always contact their own bank to dispute a charge, and the property has no way to prevent that first step. What the property can control is how well documented the booking is, which determines whether the dispute is won or lost once it is filed.
Do UPI payments face chargebacks the same way card payments do?
UPI disputes work differently and are generally less common than card chargebacks, but a guest can still raise a complaint with their bank or through the National Payments Corporation of India’s grievance process if they believe a UPI transaction was unauthorised or incorrect, so keeping proper records still matters.
What happens if a property loses a chargeback dispute?
The disputed amount stays with the guest, the property does not get the funds back, and in most cases the payment gateway’s dispute fee is not refunded either, even though the property already lost the original booking value.
Does an OTA booking’s payment gateway change who handles the chargeback?
It depends on how the payment was collected. If the OTA processed and holds the payment, the OTA typically manages the dispute. If the property collected an advance payment directly through its own gateway, the property is responsible for responding to that dispute itself.
Is a chargeback the same as a bank freezing the property’s account?
No, a chargeback only affects the specific disputed amount, which is debited from the property’s payment gateway or bank account while the case is reviewed. It does not freeze the account or affect other transactions, though a high volume of unresolved disputes can eventually lead to closer account monitoring.
Can a property charge the guest again after winning a chargeback dispute?
If the bank rules in the property’s favour, the disputed amount is simply returned to the property and the case is closed. There is no need to charge the guest again, since the original charge stands once the dispute is resolved in the property’s favour.
A chargeback is ultimately a documentation problem wearing the disguise of a payment problem. The properties that handle them well are not the ones that never face a dispute, since disputes happen even to properties doing everything right, but the ones that keep clean records of every booking and can produce them quickly when a bank asks. Pairing a reliable payment gateway with consistent booking records is the simplest way to keep the chargeback ratio low and stay in good standing with card networks. For more terms like this, visit the Resources page.