A dispute nobody replies to is a dispute you concede. We pull the evidence, write the rebuttal against the specific reason code and file it inside the deadline, on the cases where the numbers say filing is worth it.
Send us your open cases and the ones you lost last month. We will come back with what was winnable, what was not, and what the difference was worth.
Typical window to answer before the case is conceded
Varies by network and acquirer.Rounds covered: representment, then pre-arbitration
Cases filed without your sign-off on the recommendation
From a case reaching us to the pack being ready to file
Refunding is faster and sometimes it is right. The problem is doing it by default, on cases you would have won, because nobody had time to look at them.
The quiet option, and the expensive one
Worth doing where the evidence exists
Neither answer is right for every case. The point of reviewing them one at a time is that the split is rarely where merchants assume it is.
An analyst at the bank spends minutes on your case. The pack has to answer the reason code on the first screen, not bury the answer nine pages in.
For Visa 10.4 fraud claims there is a separate route. If you can show two earlier undisputed transactions from the same cardholder, at least 120 days old, sharing two identifiers such as device ID, IP address, delivery address or account login, Visa will treat the dispute as non-fraud before it ever becomes a chargeback. We check every 10.4 against this first, because winning it here is cleaner than winning it later.
An illustration of the case view. Sample data, not a real merchant.
Some codes win most of the time on two documents. Others almost never do, and filing anyway only spends your money more slowly.
| Code | What the cardholder said | What usually carries it | Worth filing |
|---|---|---|---|
| Visa 10.4 | I did not make this purchase | Matching AVS and CVV, the authentication result, device and IP tied to earlier orders, or a CE3.0 history | Often |
| Visa 13.1 | It never arrived | Tracking through to delivery confirmation, with the signature where the value required one | Often |
| Visa 13.2 | I cancelled the subscription | Your cancellation record, plus logins or usage after the date they claim they cancelled | Often |
| Visa 13.3 | It was not what was described | The product page as it stood on the order date, the spec, and your returns policy | Sometimes |
| Visa 13.6 | I was promised a refund and never got it | The refund ledger and the policy as displayed at checkout, with the message trail | Sometimes |
| MC 4837 | No cardholder authorisation | The same evidence as Visa 10.4, weighted towards the authentication data | Often |
| MC 4853 | Cardholder dispute, various sub-reasons | Depends which sub-reason was used, but the order and delivery record carry most of them | Sometimes |
| MC 4834 | Charged twice, or for the wrong amount | Settlement and authorisation records, though these are usually a genuine error at our end or yours | Rarely |
Odds here are the general pattern, not a promise. What actually decides a case is whether the specific evidence exists for that specific order, which is what the review tells you.
The network deadline starts when the notice posts to your acquirer, not when somebody opens the email. Here is where the time actually goes.
Your acquirer receives the chargeback and the clock starts. We are watching the same feed, so the case is in the queue before anyone on your side has read it.
Order, authorisation result, delivery record, message history and prior orders from the same customer come out of your gateway and cart automatically. Nobody sends us a spreadsheet.
You get the reason code, the evidence we hold, an honest read on the odds and a recommendation. Fight or refund stays your decision, and nothing is filed without it.
A rebuttal letter written against that specific reason code, not a template, with the pack assembled in the format the issuer requires and submitted through your acquirer.
The funds come back or they do not. Either way you get the reason in writing, and it feeds the next case and the reporting behind it.
Where the issuer pushes back and the amount justifies a second round, we take it. Same engagement, no new fee, and we tell you plainly when the amount does not justify it.
Win rate on its own tells you very little. What matters is the win rate on the cases you chose to file, against what filing them cost.
More than a third of the month was refunded instead. No delivery confirmation, no message trail, or an amount too small to justify the handling. Filing those anyway would have added cost and roughly nothing to the recovered figure.
An illustration built from ordinary figures, not a client result. Put your own numbers in and the split moves.
Run it on your numbersA provider paid on volume files everything. We would rather tell you where the answer is a refund, because that is where most of the wasted money sits.
The best part? Real results. We’ve seen a 40% increase in chargeback win rates since implementing their analytical tools.
Their chargeback reports helped us cut losses significantly. We now act faster, win more disputes, and stay ahead of fraud trends effortlessly.
The insights are incredibly detailed yet easy to understand. We’ve improved internal processes and reduced chargeback ratios below the industry average.
If the question is about a specific case or a specific reason code, send it over. An analyst answers, not a chatbot.
Ask us insteadWe will go through them one at a time and tell you which were winnable, what evidence would have carried them, and which ones you were right to let go. No charge for the review, and no obligation after it.
We reply within one business day. No spam, ever.