--- title: "When does a credit card chargeback work?" description: "How a dispute runs through the card network, which reasons are recognised, why a billing error differs from fraud, what the statutory protections cover and which deadlines apply." url: "https://benefitsystems.io/en/knowledge/chargeback" lang: "en" category: "Rights and disruption · Payment" domain: "reise" pillar: "rights-and-disruption" status: "entwurf" published: "2026-09-18" reviewed: "2026-09-18" type: "Artikel" --- # When does a credit card chargeback work? > **Entwurf.** Dieser Beitrag erfüllt die Redaktionsregel noch nicht vollständig und ist nicht indexiert. In the US a chargeback is a dispute inside the payment system rather than a claim against the merchant. The issuer checks whether a recognised reason applies and reclaims the amount from the merchant, who may respond. Statutory billing error rights sit alongside network rules, and both start with contacting the merchant. ## At a glance | Case | Responsible | First step | |---|---|---| | Card charged without authorisation | issuer, fraud report | freeze the card | | Service not provided | dispute through the network | contact the merchant | | Duplicate or wrong amount | billing error notice | check the statement | | Goods or service substantially different | dispute through the network | document the defect | | Price dropped later | not a payment system matter | ask the merchant | | Argument over the amount | contract law | settle in writing | ## What a chargeback is and is not A chargeback happens inside the payment system. The issuer of your card reclaims the amount from the merchant's bank through the card network. The process follows its own rules, separate from contract law. It has a fixed list of reasons, fixed deadlines and a fixed burden of proof, and those overlap only partly with any legal claim. A valid claim against a merchant is therefore not automatically a recognised reason, and a recognised reason does not replace a claim. The tool works best where the two coincide: a service that was never provided is both a breach of contract and a recognised dispute reason. The case runs between two banks, and both decide under the network's rules. The cardholder supplies documents, and a filing written as a factual record instead of a complaint shortens the handling considerably. Using the process as leverage in an argument with a merchant tends to fail, because the reviewers look for a recognised reason and evidence, and pressure is neither. ## The statutory layer US consumer credit law adds a separate route for billing errors, which sits alongside the network rules without replacing them. A billing error covers wrong amounts, charges for goods or services never accepted or delivered, and similar defects. The notice goes to the issuer in writing and starts a defined review period. While the review runs, the disputed amount cannot be treated as delinquent, and that protection is what makes the written notice worth sending even when the network route would also be open. A related statutory rule covers claims against the merchant for goods and services, with conditions that vary by situation. Both routes reward writing early and keeping copies. Network rules look similar outside the US, but the statutory protections described here are a US feature. ## The recognised reasons The recognised reasons are mainly unauthorised charges, services not provided, duplicate charges, incorrect amounts and goods or services substantially different from the description. Dissatisfaction alone is not on the list. ### An unauthorised charge A card used without consent is a fraud case, and the first step is freezing the card, not filing a form. The issuer reimburses under the rules for [unauthorised transactions](/en/glossary/card-fraud), and the process differs, as [what applies with card fraud](/en/card-fraud) sets out. Misfiling costs time. Fraud replaces the card, while a dispute leaves it in place and puts only the single charge under review, so reporting an intended payment as fraud produces a new card number and still no solution. ### A service not provided The most common travel case is the [cancelled flight](/en/glossary/flight-cancellation) or the hotel stay that never happened. The payment was intended, the service is missing. Before filing comes a written request to the merchant. The answer, or the absence of one, is the evidence the process expects, and without that record a dispute is routinely rejected. For airlines the sequence is described in [what to do when a flight is cancelled](/en/flight-cancelled-what-to-do), and the dispute sits at the end of that chain. Insolvency is where the route proves its worth. The claim against the company exists but goes nowhere, while the payment chain still functions, which makes the dispute often the only practical route. The deadline becomes the problem, because insolvency tends to become public late. Travellers with insurance pursue both routes in parallel, as [what card travel insurance covers](/en/card-travel-insurance) sets out. ### Duplicate or incorrect charges Duplicates come from technical failures, incorrect amounts from later add-ons, typically with rental cars and hotels. Evidence is easiest here, because the statement itself supplies it: two identical lines on one day speak for themselves. The merchant request still comes first. Many cases resolve there within days, because the error is obvious. Rental cars produce later charges particularly often, and which of them are justified is covered in [how card rental car coverage works](/en/rental-car-coverage). ### A substantial difference A service that differs substantially from the description is a recognised reason. The threshold sits at substantial, and it is higher than most people expect. Documentation decides these cases. Photographs, the description at the time of booking and the correspondence with the merchant belong together in the filing. The comparison runs against what was described at booking, so a screenshot of the listing taken at the time is worth more than any later account of it. Taste is not a reason. A room that feels smaller than hoped does not meet the threshold; a room without the bed that was booked does. ## How the process runs The cardholder files with the issuer, stating reason, amount and evidence. The issuer frequently posts a provisional credit and passes the case on. The merchant gets an opportunity to respond with its own evidence, such as a booking confirmation or proof of delivery. The network then decides under its rules, and the decision can reverse the provisional credit. Spending that credit as if it were final is a gamble on the outcome. Several weeks usually pass between filing and decision, and silence in that period means waiting for the other side, not losing. The counterparty is whoever appears on the statement. Where a travel site charged you, the dispute runs against the travel site, and where one seller sold a whole package, against that seller, even when an individual airline is the one that failed. Partial performance is the awkward sub-case. Where the outbound flew and the return was cancelled, only the unused part is in dispute and the amount has to be split. ## Worked example: two disputes Two payments are disputed. In the first a flight was cancelled and the airline does not reply; in the second the hotel room was smaller than expected. | | Cancelled flight | Room smaller than expected | |---|---|---| | Recognised reason | service not provided | none, if what was promised arrived | | Evidence | cancellation and unanswered request | photographs and description | | Prospects | high | low | | Effort | one filing | repeated queries | | Alternative | none needed | complain to the merchant | The flight case needs little more than two documents, the cancellation notice and the unanswered request for a refund. Together they show a service paid for and not delivered, and an attempt to resolve it that went nowhere. The hotel guest has a better route than the network. A complaint to the hotel, made on site and backed by photographs, is the alternative the table points to, and it can settle the matter while the guest is still there. Disappointment does not decide the case. The question is whether a promised service failed to arrive, and the evidence carries it: material that is understandable without explanation wins, everything else generates queries. A rejection is not final. Where new evidence appears, such as a written refusal from the merchant, the issuer can resubmit while the deadline is still open. ## Deadlines Deadlines are the most common reason for rejection, and they are shorter than any ordinary limitation period. The start depends on the route. A statutory billing error notice runs from the statement showing the charge, while network rules often run from the date the service was due. Bookings far in advance create a trap, because paying a year ahead can exhaust the payment system route before the trip even starts. A calendar entry on the service date recalls the deadline while the case is still open. File as soon as it is clear that a service will fail. A flight that operates after all can be withdrawn from dispute; a missed deadline cannot be repaired. A merchant who is slow to answer is no reason to let the window close either: filing protects the claim, and the dispute can still be withdrawn if the refund arrives. Compensation claims run separately. Compensation follows the law of the journey, a dispute follows network rules, and they examine different questions. Documents assembled for an insurance claim can be reused for the dispute, so the effort happens once without anything being reimbursed twice. ## When it is not worth filing a dispute Filing is not worth it in these situations: - **Mere dissatisfaction.** Without a missing or substantially different service there is no recognised reason. - **Later price changes.** A price that dropped afterwards is not a payment defect. - **When the merchant is already refunding.** Filing while a [refund](/en/glossary/refund) has been promised creates two processes, double credits and eventually a clawback. - **Arguments over the amount.** A disputed sum belongs in contract law, outside the payment system. - **After accepting a voucher.** Taking a voucher instead of cash usually removes the dispute reason, as [voucher instead of cash](/en/voucher-vs-cash) describes. Small amounts are a matter of judgement. The deadline applies to them as well, but whether to spend an hour on the filing is a question of your own time. Repeated filings without results eventually draw a review of the customer, and filing frequently without grounds can lead to the account being closed. The process is built for exceptions. It enforces a claim faster than any other route, but only where the facts are visible without interpretation. ## What makes a filing strong Everything that decides the outcome exists before the filing. The written request to the merchant, with a date, evidences the attempt to resolve and belongs in every file. Proof that the service failed comes next: for flights the cancellation, for hotels the refusal, for goods the missing delivery. The statement with the line marked ties the case to the payment and makes the review short. A brief statement of facts completes it. Three sentences with date, service and failure are enough, and every extra line raises the chance of a query. Several charges are listed one by one, each with date and amount. A bulk filing without a schedule produces queries and adds weeks. ## The most common mistakes - **Skipping the merchant.** A written request comes first, and the answer belongs in the file. - **Waiting too long.** The deadline can run from the service date, so filing early is the only safe course. - **Confusing a dispute with fraud.** Only a charge made without consent is fraud. - **Filing without evidence.** Request, proof and statement go in together. - **Treating the provisional credit as the end.** It stays provisional until the network decides. - **Running two routes at once.** A merchant refund and a dispute for the same charge end in a clawback. ## Related topics - [What to do when a flight is cancelled](/en/flight-cancelled-what-to-do) - [Voucher instead of cash](/en/voucher-vs-cash) - [What applies with card fraud](/en/card-fraud) - [What card travel insurance covers](/en/card-travel-insurance) - [How card rental car coverage works](/en/rental-car-coverage) - [What applies to denied boarding](/en/denied-boarding) ## Frequently asked questions ### What is a chargeback? A dispute inside the payment system. Your issuer reclaims the amount from the merchant's bank through the card network when a recognised reason applies. The merchant may respond, and a defined process then decides the case. ### Which reasons are recognised? Mainly unauthorised charges, services not provided, duplicate charges, incorrect amounts and goods or services substantially different from the description. Dissatisfaction alone is not one of them. ### Do I have to contact the merchant first? In nearly every case yes. The process expects evidence that you attempted to resolve it, and without that record a dispute is routinely rejected. ### What is a billing error? A statutory category in US consumer credit law covering wrong amounts, charges for goods never delivered and similar defects. It carries its own written notice procedure and its own deadline. ### How long do I have? Statutory billing error notice runs from the statement showing the charge, while network rules often run from the date the service should have been provided. Both are shorter than any ordinary limitation period. ### Is a dispute the same as reporting fraud? No. Fraud means the card was used without authorisation, and the card gets replaced. A dispute means the payment was intended but the service was not delivered as agreed. ### Can the merchant fight it? Yes. They submit evidence such as a booking confirmation or proof of delivery, and the network decides. A first credit is therefore provisional. ### Do I get the money back immediately? Usually a provisional credit appears while the case is open. It can be reversed if the merchant prevails. ### Does it help when an airline fails? It is often the only practical route, because a claim against the company itself goes nowhere. The deadline becomes the problem, because insolvency tends to become public late. ### What about a booking made through a travel site? The name on the statement decides. Where the travel site charged you, the dispute runs against the travel site rather than the airline. ### Will disputing hurt my relationship with the issuer? With the merchant possibly, with the issuer usually not. Filing frequently and without grounds can lead to the account being closed. ### Does this apply outside the US? Network rules are similar elsewhere, the statutory protections are not. This article describes the US position with its billing error rules.