Payments
Representment
Representment is the process of contesting a chargeback by submitting evidence to the issuer that the original transaction was valid and authorized.
Success depends almost entirely on evidence assembled at transaction time rather than at dispute time: authorization records, delivery confirmation, the terms the customer accepted, and communication history.
Deadlines are unforgiving and set by the network, not the merchant. A dispute where evidence is compiled manually after notice arrives is frequently lost to the clock rather than to the merits.
This is why representment is really a data-capture problem wearing a legal costume. The merchants who win are not the ones writing better rebuttals; they are the ones whose systems already recorded the authorization result, the delivery confirmation, the version of the terms the customer accepted and the IP and timestamp of the order — and can assemble that automatically the moment a dispute is filed. Deciding to collect that evidence after the first loss is deciding to lose the first several.
Where representment sits in the dispute lifecycle
The word describes one specific stage, and the stages either side of it change what the stage is worth. Before a chargeback exists there is a pre-dispute layer. The networks and third-party services notify merchants that a cardholder has raised a claim, and give a short window to refund before the dispute is filed. Some of them resolve the claim by pushing order detail into the cardholder's banking app, which frequently ends the matter, because the cardholder simply did not recognise the descriptor. Nothing at the representment stage is as cheap as anything at this one.
The chargeback itself is the issuer filing under a reason code. Funds are debited, a fee is charged, and the merchant is given a response window. Representment is the merchant re-presenting that transaction to the issuer with evidence that it was valid — literally presenting it a second time.
If the issuer accepts, the funds return. If the cardholder maintains the claim, the case escalates to pre-arbitration and then to arbitration, where the network decides and the loser pays a filing fee that on a typical direct-to-consumer order exceeds the order value. Escalating a small dispute past the first round is rarely rational arithmetic.
One structural point shapes how the whole process behaves. Visa splits disputes into allocation and collaboration. Fraud and authorisation disputes are allocated — the network resolves them largely on transaction data, and a merchant with no liability shift and no supporting data can lose before writing anything. Processing-error and consumer disputes are collaborative, and there the evidence a merchant supplies is the substance of the case.
What representment actually is, and who reads it
It is not an appeal to a neutral tribunal. In the first round the merchant's submission is reviewed by the issuing bank — the cardholder's bank, which has already credited the cardholder and has no institutional interest in reversing that.
That reality determines the form. The reviewer is working through a queue with minutes per case, against a specific reason code, looking for whether the merchant has rebutted the specific claim. A narrative explaining that your business is legitimate rebuts nothing. A document set matched to the reason code, with the decisive facts on the first page, is the only shape that survives the queue.
It also determines what is winnable. Where the cardholder's claim is factually wrong and you hold the record proving it — the goods were delivered to their verified address, the cancellation they claim to have made was never submitted, the authorisation they say did not exist has a code and a timestamp — representment works. Where the claim is essentially true but you disagree about fairness, it does not, and the attempt costs staff time and an escalation risk on top of the loss.
What evidence wins, by dispute family
Evidence is only persuasive if it answers the question the reason code asks. The same delivery record that decisively wins a non-receipt dispute is irrelevant to an authorisation dispute, and submitting it there reads as a merchant who has not understood the claim.
The Visa condition codes below are used as the reference numbering; Mastercard and the other networks group disputes into the same families under their own codes.
| Family | What the issuer is asking | Evidence that decides it | What never helps |
|---|---|---|---|
| Fraud, card-absent (10.4) | Was the genuine cardholder in control of this order? | Authentication result and liability shift, AVS and CVV match, device and IP matching prior undisputed orders on the same account, delivery to the verified billing address | Describing your fraud tooling |
| Authorisation (11.1–11.3) | Was there a valid approval for this amount? | The authorisation record: code, timestamp, amount, and proof the capture matched it and fell inside its validity | Any argument about the merits of the sale |
| Processing error (12.1–12.7) | Was the amount, currency, date or count correct? | Settlement records, the checkout page showing the currency and amount the customer selected, evidence that a claimed duplicate is a distinct order | Delivery evidence |
| Goods not received (13.1) | Did this reach the cardholder? | Carrier tracking showing delivery to the cardholder's address, with signature or proof-of-delivery image and the carrier's own record | A shipping label with no delivery scan |
| Cancelled recurring (13.2) | Did the merchant charge after a cancellation? | The cancellation terms accepted at signup, the record that no cancellation request was received, renewal reminders sent, and evidence the service was used after the disputed date | A policy the customer was never shown |
| Not as described or defective (13.3) | Did the customer receive what was advertised? | The product page as it stood on the order date, order photographs, the returns policy accepted, and the support thread | A current product page that has since been edited |
The deadline that binds is your processor's, not the network's
Networks publish a response window measured from the chargeback date. That is not the date you should be working to. Your acquirer or processor has to review and file the response inside that window, so its internal cut-off is earlier, sometimes by several days, and it is the one that actually ends your opportunity.
Deadlines are also not uniform. They differ by network, by dispute family and by the stage of escalation, which means a single dispute-handling SLA applied to every case will be comfortable for some and already expired for others.
The compelling-evidence provisions add a further, sharper constraint. Visa's programme allows certain card-absent fraud disputes to be answered with two prior undisputed transactions on the same credential, sharing identifiers such as device ID, IP address, delivery address or customer account ID, and aged inside a window the network defines. Every element of that has to have been captured at order time, on transactions that happened months earlier. There is no way to assemble it after the dispute arrives — either your checkout recorded device and IP against the account on every order, or that route is closed to you and you did not find out until you needed it.
This is the whole reason representment is a systems problem rather than a writing problem. The submission has to be assembled from records that already exist, in days, by a process that does not depend on someone remembering where the delivery confirmation is stored.
Why a refund before the dispute is usually the cheaper outcome
When a pre-dispute alert arrives, the choice is to refund now or to let the chargeback land and contest it. That decision has an arithmetic answer, and the arithmetic is uncomfortable for the instinct to fight.
Take an example order of 90 dollars, with 40 dollars of goods and fulfilment already spent, 3 dollars of payment fees that are not returned, and a chargeback fee of 15 dollars. Refund before the dispute: the revenue reverses, the goods are gone, the fees stay gone, and the position is minus 43 dollars. Lose the chargeback: the same, plus the 15-dollar fee, so minus 58 dollars. Win the representment: the 90 dollars stays, less 40 of cost and 3 of fees, and the chargeback fee is typically not returned, so plus 32 dollars.
Measured against the refund baseline of minus 43, winning is 75 dollars better and losing is 15 dollars worse. Representment beats refunding when the expected gain exceeds the expected loss: 75p is greater than 15 multiplied by one minus p, which resolves at p above one sixth — roughly a 17 per cent win probability on these inputs.
That threshold looks easy to clear until two things are added. The dispute is counted against the ratio the moment it is filed, whether you win or lose, and the ratio is what brings reserves and monitoring programmes. And the staff time spent assembling a submission is real. Both push the true break-even well above 17 per cent, which is why the correct policy on most direct-to-consumer books is to refund on alert by default and represent only the families where the evidence is documentary and the win rate is measured rather than assumed.
Frequently asked questions
- What is representment?
- Representment is a merchant contesting a chargeback by presenting the transaction to the issuing bank a second time, with evidence that the original charge was valid and authorised. The issuer reviews the submission against the specific reason code it filed under. If it accepts, the funds return to the merchant; if the cardholder maintains the claim, the case escalates to arbitration.
- What is the difference between representment and a chargeback?
- A chargeback is the cardholder's bank reversing a payment. Representment is the merchant's response to it — re-presenting the same transaction with supporting evidence. The chargeback comes first and moves the money immediately; representment is the only mechanism by which the merchant can get it back, and it operates inside a deadline the network and the merchant's processor set.
- What evidence wins a chargeback representment?
- Evidence that answers the specific reason code. Non-delivery disputes turn on carrier tracking showing delivery to the cardholder's address with proof of delivery. Authorisation disputes turn on the authorisation code and timestamp. Cancelled-subscription disputes turn on the accepted terms, the renewal reminders sent, and the absence of a cancellation request. All of it must have been recorded at order time.
- How long do you have to respond to a chargeback?
- The network sets a response window running from the chargeback date, and it varies by network, dispute family and escalation stage. The binding deadline is earlier: your acquirer or processor must review and file inside that window, so its internal cut-off is the one that ends your opportunity, sometimes several days ahead of the network date.
- Should I refund instead of fighting a chargeback?
- Often yes, when a pre-dispute alert gives you the option. Refunding costs the sale and the goods but avoids the chargeback fee, the staff time and the count against your dispute ratio. Contesting is worth it only where the evidence is documentary and your measured win rate on that dispute family is high — not where you simply believe the claim is unfair.
- Does winning a representment remove the chargeback from my ratio?
- Generally no. Network monitoring programmes count disputes from the date they are filed, so a dispute you win still contributes to the ratio that triggers reserves, monitoring and fees. Winning returns the transaction amount, and usually not the chargeback fee. This is the arithmetic that makes prevention worth more than a good representment process.