CHARGEBACKS
The Chargeback Lifecycle and How Representment Actually Works
A chargeback moves through fixed stages with a deadline on each one, and the reason code on the notice decides which evidence has any chance of winning.
A customer told their bank the charge was wrong, and the money left your account before anyone asked you anything. That is the part owners find hardest to accept, and it is by design. The cardholder's bank moves first, you are notified second, and your opportunity to answer comes third.
What follows is a defined sequence with a deadline attached to every stage. You can win at several of those stages and you can lose at all of them by missing a date. The reason code printed on the notice governs everything else, because it tells you which bank made which accusation, and therefore which documents mean anything.
What happens, in order
- The cardholder calls the issuer. Sometimes about fraud, more often because the charge on the statement does not look like the business they remember paying.
- The issuer decides. It either resolves the matter with its own customer or files a chargeback against your acquirer. On some claim types the issuer first sends a request for information, which is a cheaper stage for you and should always be answered.
- The money is pulled. Your acquirer debits the transaction amount from your account and adds a chargeback fee. This happens before you have said anything.
- You get the notice. It carries the reason code, the amount, the cardholder's stated grounds and a response date.
- You choose. Accept the loss and stop spending on it, or represent the transaction with evidence.
- The issuer reviews your evidence. If it accepts, the amount is credited back to you. If it does not, the case stays lost.
- The issuer can escalate. A case that has been represented can go to a further round and then to arbitration by the card network, which carries fees large enough to make a small ticket not worth defending.
That last line is a real decision, not a defeatist one. Work out the total exposure on a case before you defend it, and put your hours where the amount justifies them.
The reason code decides what evidence counts
Reason codes group into a few families, and each family is won with completely different paper.
Fraud claims. The cardholder says they did not authorize the charge. For a card present sale, a chip transaction read properly by the terminal usually puts the fraud loss on the issuer, while a keyed sale or a forced swipe pulls it back to you. For an online sale, you are assembling identity: address verification and security code results, the authentication result if you used one, the device and network details captured at checkout, the delivery address matching the billing address, and any prior orders from the same account that were never questioned. That history of quiet prior orders carries real weight in the current network evidence standards.
Authorization problems. The sale was settled without a valid approval, or after the approval had aged out, or for more than the approved amount. These are hard to win because the record is machine generated and it either exists or it does not.
Processing errors. Duplicate charges, wrong amount, wrong currency, a credit that was issued but never reached the account, a transaction deposited outside the clearing window. Your own batch records answer most of these in minutes.
Consumer claims. Goods not received, service not rendered, item not as described, a recurring charge after cancellation. Delivery proof wins the first. The listing, the terms the buyer agreed to and the message history win the second. A cancellation log with a timestamp wins the third.
Send the wrong family of evidence and you lose a case you should have won. A signed delivery receipt is worthless against a fraud claim, because nobody said the parcel failed to arrive, and a photograph of the product is worthless against an authorization code that was never obtained.
Assembling the representment file
The person reading your submission works at the issuing bank, has a queue, and is not invested in your business. Write for that reader.
Open with a short statement of what the transaction was and why the cardholder's grounds do not fit the facts. Reference the reason code by number. Then attach the evidence in the order you referenced it, with the relevant line highlighted rather than buried in twelve pages of log export. Strip out anything that is not responsive. A file that makes the reviewer hunt gets decided against you.
Keep the tone flat. Nobody at the bank cares that the customer was rude, and moral arguments do not move a reason code. Facts, dates, documents.
Two mechanical points decide more cases than the writing does. Submit through the exact channel your acquirer specifies, because a packet emailed to a relationship manager often never reaches the queue it needed to reach. And confirm the portal accepted what you sent, because uploading is not the same act as filing. A file sitting in a draft state looks identical, from the network's side, to a merchant who never answered at all.
The money and the ratios
Two costs sit behind every chargeback. The first is the fee, which you pay regardless of outcome. The second is the ratio.
The card networks track the number of chargebacks you take against the number of transactions you run, and when that ratio passes the published thresholds they place the account into a monitoring program. Those programs come with monthly charges that climb the longer you stay in them, required remediation plans and, at the far end, the loss of your ability to accept cards at all. Winning cases does not remove them from the count in the way most owners assume. The ratio is measured on chargebacks received.
That is the reason prevention outranks defense, and it is why a business with a low ticket and a high claim rate can be profitable on paper and still lose its account.
Cutting them off upstream
- Fix your billing descriptor first. More claims start with an unrecognized line on a statement than with actual fraud. Your descriptor should carry the name the customer actually saw, plus a phone number they can reach.
- Refund faster than the bank can act. A refund issued before the chargeback posts costs you the sale. A chargeback costs you the sale, the fee and a mark on the ratio.
- Answer information requests immediately. They are an off-ramp, and ignoring one converts it into the expensive version.
- Capture delivery proof on anything worth defending. Signature on higher value orders, tracking on everything else, and an access log on anything delivered digitally.
- Make cancellation genuinely easy on recurring billing. A customer who cannot find the cancel button uses their bank as the cancel button.
- Look at network alert programs. These push a notice to you while the claim is still forming, giving you a short window to refund and stop the case. They cost money per alert and they earn it on a business that takes cards online.
And keep your own log. Every claim, the reason code, what you sent, what came back. After a few months that file tells you which product, which channel or which sales script is actually generating your chargebacks, which is a question no processor report will answer for you.
Common questions
how long do i have to respond to a chargeback
The card network sets the outside limit and your processor usually sets an earlier internal cutoff so it has time to file, which means the only date that governs you is the one printed on the notice you received. Missing it is an automatic loss with no appeal, even on a case you would have won easily. Treat the notice as the clock and calendar it the day it arrives.
do i get my money back if i win a chargeback
You get the transaction amount back, credited to your account by your acquirer after the issuer accepts your evidence. You do not get the chargeback fee back, and that fee is charged whether you win or lose. The case also still counts toward the chargeback ratio the card networks monitor, which is why winning a lot of them is not the same as being in good standing.
what is representment in payment processing
Representment is the stage where you send the transaction back to the issuing bank with evidence that the original charge was valid, which is why it is also called second presentment. You are not arguing to a judge or to the card network, you are handing a file to the bank that pulled the money, and that bank decides. If it rejects your evidence, the issuer can escalate the case further rather than ending it.