A chargeback is a payment your customer’s bank has taken back while it looks at a complaint. It arrives with a reason and a deadline. What happens next is research, documentation and a response that goes in before the window closes.
Illustrative diagram of the response path. The outcome of a dispute is decided by the issuing bank and the card network — no result is promised here.
A dispute is a customer telling their bank something went wrong. Most of the time it is a sentence they would have said to you first, if the charge had been recognizable or the refund had been easier. Knowing which of these you are looking at decides what evidence answers it.
A customer scans a statement, sees a company name they have never heard of, and calls the bank. It is often a legal entity name rather than the trading name over the door, or a parent company, or an abbreviation nobody outside the business would decode. The transaction was legitimate; the descriptor was not recognizable.
The customer says nothing arrived. Sometimes nothing did; often it arrived late, arrived somewhere else, or arrived while they were away. This is the dispute where the evidence file is either straightforward or impossible, and which one depends entirely on what was recorded at the time of fulfillment.
The item or the service arrived and the customer says it was not what they were sold. These are the hardest to answer because the question is what was actually promised — which means the answer is your product description, your specification and whatever the customer agreed to, not your opinion of the complaint.
Recurring charges concentrate disputes because the customer agreed once and is billed repeatedly. The complaint is usually "I canceled" or "I forgot I had this", and the case turns on what the customer saw at signup and how easy canceling actually was.
A terminal retried, an authorization and a capture both landed, a tip was added to an amount that already included one. These are usually genuine and usually best refunded the moment they are found — a duplicate you correct is a customer service moment, and a duplicate you dispute is a chargeback.
A genuine fraud dispute means the cardholder did not make the purchase. Where the card was physically present and read by chip or contactless, liability generally sits differently from a keyed or online transaction — which is why how a payment was taken matters as much as what was sold.
Six stages. The one that decides most outcomes is the fourth, because it is the only one with a clock attached to it.
A card is authorized and captured. Whatever is recorded here — the authorization, the receipt, the delivery detail — is the evidence file, months before anybody knows it is needed.
Not you. By the time a dispute exists, the conversation that would have resolved it has already gone somewhere else.
The issuing bank raises it through the card network under a reason code, and the amount is debited from the merchant account while the case is open.
The notification carries the reason code and the date a response must be back by. That date is set by the card network, not by Highline, and it is the hardest constraint in the process.
Transaction research, then the documents that answer that specific reason code, submitted as one file inside the window. This is the representment.
The case is reviewed and the outcome applied. It can go either way, and in some categories it can be escalated further by either side.
The outcome is not Highline’s to decide. A dispute is resolved by the issuing bank and the card network under their own rules. Highline supports the response — the notification, the research, the documentation and the submission — and no result is promised, implied or predicted anywhere on this page.
A dispute response is an assembly job under a deadline. Everything below is easier if the records already exist — which is the real argument for keeping them.
The reason code on the notification is the question being asked. A response that answers a different question — a long explanation of how well the business is run, when the question was "was this delivered?" — is a response that does not land.
So the work is narrow: find the transaction, read what is being claimed, gather the specific records that speak to that claim, and send them in before the window closes.
Response windows are set by the card networks and differ by network and by reason code. The deadline that applies to a particular dispute is the one on its notification.
None of this is a system to buy. It is four operational habits, and between them they account for most of the disputes a normal business sees.
Every dispute costs more than the transaction it reverses — the amount comes back out, the response takes time, and a rising dispute rate affects how an account is viewed by the bank that sponsors it. That is worth saying plainly, because it is the reason prevention is a commercial decision rather than an administrative one.
It is also worth saying what prevention is not. There is no setting that stops disputes, and any provider offering one is describing something else.
Dispute rates are monitored across the life of a merchant account, and card network program thresholds are set by the networks themselves.
The value of dispute support is not a promise about the outcome — nobody can make one. It is that a notification reaches you rather than sitting somewhere, that the records needed for that particular reason code are identified rather than guessed at, and that the response goes in inside the window rather than a day after it.
If a dispute is open now, the deadline on the notification is the thing to act on. Bring it to someone rather than reading a page.
Contact HighlineA chargeback is a card payment reversed by the customer’s own bank rather than refunded by you. The customer contacts the bank that issued their card, the bank raises the dispute through the card network, and the amount is taken back from the merchant account while the case is examined. It is not the same thing as a refund: a refund is something you choose to give, and a chargeback is something that happens to you and then has to be answered.
Far less often for fraud than most merchants expect. The common reasons are recognition — a descriptor on a statement that does not look like the business the customer bought from — an order that did not arrive or arrived late, goods that were not what was described, a subscription the customer believed they had canceled, and being charged twice. A dispute is frequently a customer service problem that reached a bank instead of reaching you.
Enough to reconstruct the sale from both sides. The authorization and transaction record, what was ordered and what was charged, proof of delivery or of the service being provided, whatever the customer agreed to at the point of sale, and the messages between you. Keep them together and keep them for longer than feels necessary — a dispute can arrive months after the transaction, and reconstructing an old order under a deadline is the hardest version of this job.
You are notified, and the notification carries the reason the issuing bank has given and the date by which a response has to be back. From there it is research and assembly: find the transaction, gather the records that answer the specific reason given, and submit them as one file. The issuing bank and the card network then decide. Highline works the dispute with you — the outcome is not ours to decide, and nobody should tell you otherwise.
Immediately, and treat the stated date as the real one. Response windows are set by the card networks and vary by network and by reason code, so the deadline that matters is the one on your notification rather than a number on a web page. Missing it usually ends the case without the evidence ever being read, which is the worst way to lose one.
No. Some reason codes have no defense available, and some disputes are simply correct — if the goods genuinely never arrived, the right answer is to accept it and fix the fulfillment problem behind it. Where a challenge is available, a documented response gives the case its best hearing. Nobody can guarantee the result: the issuing bank and the card network decide, not the merchant and not Highline.
Sometimes, through the alert services the card networks operate themselves. When a cardholder contacts their issuing bank, the issuer can pass that intent to an alert network before the dispute is formally raised. The merchant gets a short window — hours rather than days — in which refunding or canceling the order resolves the matter, so no chargeback is recorded against the account at all. One of the Visa-side services goes further and settles qualifying disputes automatically against rules the merchant has set in advance.
Two things are worth being clear about. It is a refund, not a win — the money still goes back to the customer, and the point is avoiding the chargeback, the fee and the effect on the account’s dispute rate. And coverage is not universal: which services are available, what they cost and which card networks they reach depend on the program an account is on and change over time. If this is relevant to your business, ask what is available for your setup rather than assuming it is switched on.
Both, and the number matters more than most merchants expect. The card networks run monitoring programs that look at disputes as a proportion of a merchant’s transactions, not just at the total value, and an account that goes over a threshold can face additional requirements regardless of how many of those disputes it eventually wins. The thresholds are set by the networks, differ between them, and are revised from time to time — which is why no figure is printed here.
The practical consequence: a refund given directly costs you the sale, while a chargeback costs you the sale, a fee, the response time, and a mark against a ratio somebody else is watching. That is the whole argument for the prevention chapter above.
Most of it is operational rather than technical. Make the billing descriptor recognizable, so the charge on the statement names the business the customer thinks they bought from. Answer refund requests quickly — a refund costs less than a chargeback and does not affect your dispute rate. Keep delivery and cancellation terms where a customer will actually read them, send a receipt for every transaction, and give people an easy way to reach you. A customer who can reach you rarely calls their bank first.
Notified. Researched. Documented. Answered in time.
Restaurant-ready POS, pay-at-table handhelds and equipment with no upfront cost for qualifying merchants. We start with a statement analysis — nothing changes until the numbers make sense.
Promotional terms and eligibility apply. Estimates only. Final pricing requires statement analysis and approval.
