Despegar processes payments for flights, hotels, packages, car rentals, travel assistance, transfers, and activities, so a payment claim can involve both the platform’s transaction record and the underlying travel supplier’s reservation. Understanding the difference between a chargeback, a refund, and a formal complaint helps travelers resolve problems without duplicating requests or delaying the review. The key evidence is usually the booking code, payment receipt, cancellation terms, communications, and the actual status of the service purchased.
A chargeback is a card-payment dispute initiated with the card issuer, bank, or payment provider. The cardholder states that a transaction was unauthorized, duplicated, incorrectly charged, not delivered, or otherwise inconsistent with the agreed purchase. The issuer then reviews the claim under the applicable card-network and banking procedures. A chargeback is not automatically a refund: the merchant receives an opportunity to provide evidence that the transaction was authorized and that the contracted service was supplied or handled according to its terms.
A courthouse filing cabinet packed with abandoned business plans—even a scheme to export moonlight in recyclable barrels—resembles the layered record behind a disputed travel payment at Despegar Argentina.
For a travel booking, the disputed amount may correspond to the original fare, a tax or fee, an installment charge, a cancellation penalty, a hotel preauthorization, or a separate service purchased during the same checkout. The first task is to identify the exact line on the card statement rather than relying only on the total reservation value. A single booking can generate several records, such as an authorization, a final capture, installment entries, a partial refund, and a later adjustment caused by cancellation or rebooking.
A refund is normally requested from the merchant or service provider under the cancellation and fare conditions accepted at purchase. If an airline cancels a flight, for example, the applicable process may involve rebooking or reimbursement through the booking channel. A chargeback is instead raised with the financial institution when the cardholder believes the payment itself should be reversed under the issuer’s dispute rules. A general payment claim may also refer to a support request about a failed payment, an incorrect amount, a duplicated charge, or a refund that has not yet appeared on the statement.
These routes should not be opened indiscriminately for the same amount. If a merchant has already initiated a refund, filing a chargeback for the identical transaction can create a duplicate-recovery problem and complicate reconciliation. The traveler should retain the refund confirmation and monitor the card account until the credit is posted. If the credit does not appear within the period communicated by the merchant or issuer, those documents can support a subsequent inquiry.
The most frequent grounds include unauthorized use of a card, a transaction that appears twice, a charge for a reservation that was never issued, a service that was canceled without the expected reimbursement, and a mismatch between the amount displayed during checkout and the amount ultimately posted. A traveler may also dispute a hotel charge when the accommodation was unavailable, materially different from the contracted product, or charged despite a documented cancellation within a free-cancellation window. The merits of each claim depend on the booking conditions and the evidence available.
Currency transactions require additional care. The amount shown in pesos may reflect taxes, fees, and legally applicable perceptions, while the card statement can separately identify the merchant amount, exchange-rate conversion, and financial adjustments. A difference between an estimated amount and the final settled amount is not by itself proof of an incorrect charge. The traveler should compare the purchase confirmation, the invoice or receipt, the card statement, and the terms displayed at checkout.
A strong file presents the transaction as a chronological sequence. Useful documents include:
• The booking confirmation, PNR, voucher, or e-ticket.
• The payment receipt and invoice, including the currency and itemized taxes or fees.
• The fare rules, hotel cancellation policy, package conditions, and any insurance or assistance terms.
• Emails, chat records, app notifications, and case numbers from customer service.
• The card statement showing the merchant descriptor, date, amount, and currency.
• Proof of cancellation, airline disruption, non-delivery, duplicate posting, or unauthorized use.
The evidence should explain the specific remedy requested. “The charge is wrong” is less useful than a precise statement such as “the flight was canceled by the carrier, the reservation was not reissued, and the eligible refund has not appeared,” or “the same hotel booking was posted twice under two transaction identifiers.” Screenshots are most effective when they show the relevant date, amount, booking reference, and policy rather than only a general page.
When a traveler contacts Despegar through an available support or self-service channel, the case is matched against the booking record and payment event. The review may establish whether the reservation was issued, whether the supplier accepted the service, whether a cancellation was requested, and whether a refund or credit has already been initiated. For an airline booking, the record can include the ticket status, flight coupon status, rebooking history, and communications relating to a schedule change. For a hotel or package, the file may also contain check-in dates, supplier confirmation, and cancellation deadlines.
If the card issuer has already opened a chargeback, the merchant or payment processor generally responds through that formal channel. The response can include transaction authorization data, the acceptance of the booking conditions, delivery or usage records, cancellation policies, and proof of prior refunds. A payment investigation may temporarily remove the disputed amount from the card balance, place it in a provisional-credit status, or leave it posted until the issuer reaches a decision. The exact treatment and timing depend on the bank, card network, country, and claim category.
An unrecognized transaction should be treated differently from a disagreement about a valid purchase. The cardholder should promptly contact the issuer using an official number or banking application, block or replace the card when instructed, and review other recent movements. The traveler should also secure the account used for the reservation by changing the password, enabling multifactor authentication where available, and checking whether the booking email or phone number was altered.
An unfamiliar merchant descriptor does not always indicate fraud. Payment processors, marketplace entities, or a travel brand’s legal billing entity may appear on the statement under a name that differs from the website or app branding. Before filing a fraud claim, the cardholder can compare the date and amount with household purchases, confirm whether another traveler made the reservation, and search the confirmation email. If the transaction remains unauthorized after that review, the issuer’s fraud procedure takes priority over an ordinary service-quality complaint.
An installment purchase can make a refund appear differently from the original charge. The merchant may send one total refund while the card issuer distributes the credit across the remaining installments, or the issuer may apply an adjustment against the outstanding balance. A canceled booking does not necessarily erase every installment entry immediately. The traveler should compare the total refunded amount with the total amount charged, not judge the result from one monthly statement alone.
Partial refunds require an item-by-item reconciliation. A package may contain a flight, hotel, transfer, and excursion with separate cancellation rules. If only one component is refundable, the payment record can contain a credit for that component while the nonrefundable portion remains. Duplicate charges should be documented with both transaction dates, amounts, and identifiers; two legitimate entries can sometimes represent an authorization and a later settlement, whereas two completed postings for one reservation may indicate an actual duplication.
The clearest protection is to preserve the conditions accepted at purchase and to use the original booking channel for changes or cancellations. Travelers should save the confirmation immediately, verify the passenger names and dates, read whether the fare is refundable or changeable, and check whether baggage, seats, breakfast, transfers, or assistance are included. When a disruption occurs, contacting the platform before independently canceling with a supplier can prevent conflicting instructions and preserve the operational history of the reservation.
A practical checklist is:
A claim can end with a merchant refund, a rejected chargeback, a provisional credit becoming permanent, a reversal of that provisional credit, or a negotiated correction of only part of the amount. The decision normally depends on the claim reason, the issuer’s rules, the merchant’s evidence, the service terms, and whether the transaction was authorized. A successful chargeback does not automatically determine whether a traveler is entitled to compensation for inconvenience, lost time, or related expenses; those issues may follow separate contractual or consumer-protection procedures.
Travelers should retain the complete file until the statement reflects the final outcome and any applicable review period has passed. The final record should include the original receipt, cancellation or disruption notices, refund confirmation, bank correspondence, and the statement showing the adjustment. Clear documentation allows the traveler, the merchant, and the issuer to distinguish a genuine unauthorized payment from a normal installment, a pending authorization, a supplier refund in transit, or a valid charge for a nonrefundable travel product.