WorkflowCustomer Service Automation

Chargeback Management

Chargeback management software that fights the disputes worth fighting, with every exhibit cited

More chargebacks won, weak ones accepted fast, and no dispute left to expire.

See one case, screen by screen ↓
demo78%win odds on a $612.40 Visa 10.4 fraud claim once the agents qualified it for Compelling Evidence 3.0 — it was 31%
demo61disputesbrought in overnight from three processors, priced, with 44 packs drafted and checked before the analyst sat down
estimated$1.55Mmore recovered a year: more of the right disputes fought, and more of them won
target0expireddisputes left to expire, with the dispute ratio held under the network threshold
In short

What is Chargeback Management?

Software that takes a card dispute from the processor's notice to a decision: fight it with a representment response, accept it, or prevent the next one. Chargeback Management adds seven agents that bring every dispute in with its true deadline, price fight or accept, fill the evidence the reason code requires, draft the response and check it as the issuer would — while the chargeback analyst decides and signs.

How to choose AI solutions for back-office and enterprise work →

Updated

The problem

Why good disputes are lost and bad ones are fought

A merchant that takes cards gets disputes every day from several processors, each under one of dozens of network reason codes with its own evidence rules and an earlier processor deadline. The analyst opens each one in a processor portal, decides by feel whether it is worth fighting, then hunts for the order, the delivery scan, the sign-in and the service notes across five systems, pastes them into a template letter and uploads it — often in the last two days of the window.

So weak cases are fought and lost, strong ones go out without the one exhibit the reason code needs, and some expire unanswered. A Visa 10.4 fraud claim that would qualify for Compelling Evidence 3.0 is answered as a plain fraud claim, because finding two earlier undisputed orders on the same card, from the same device or IP address, takes longer than anyone has. Outcomes come back weeks later in a processor report, and nobody ties a loss to the missing exhibit or a repeat disputer to the checkout rule that let them through.

typical324Ma yearchargebacks expected worldwide by 2028
typical$4.61per $1what US merchants lose for every dollar of fraud
typical45%of chargebacks merchants reported as fraud
Where a dispute's calendar days goestimated
By hand17 days
With the solution1 days
  • Waiting in a processor portal before anyone opens it6 → 0.1 d
  • Deciding whether it is worth fighting2 → 0.1 d
  • Finding the order, delivery, sign-in and service notes5 → 0.3 d
  • Writing the response from a template2 → 0.2 d
  • Review, sign-off and upload2 → 0.3 d

Estimated split of the roughly 17 days a response took by hand at the demo company, against the one-day target with the agents.

How it works

How a dispute moves

Seven agents price every dispute, fill the evidence the reason code requires and check each other's work; the analyst decides and signs.

What comes in
Sources in10 systems · processors, orders, carriers, sign-ins, devices, service desk
Agents at work
Intake agenttrue deadline
Then
Triage agentfight or accept, priced
Then
Evidence agentfills every socket
Drafting agentthe response
Then
Critic agentreads as the issuer
Pattern agentrepeat disputers
Outcomes agentwins, money, ratio
A person decides
Chargeback analystsubmits, sends back or accepts with a reason code
What comes out
Response submitted
Weak disputes accepted fast
Recoveries matched to the ledger
One case, step by step

One fraud claim, from overnight intake to a signed response

Kestrel & Vane Group sells through four card-accepting businesses and three processors. On Wednesday morning a $612.40 Visa 10.4 fraud claim on a cordless tool kit is waiting for Daniel Okafor. Here is what happens next, screen by screen, in the working solution.

  1. 01Wednesday morning

    The agents worked the night; six decisions need him

    Daniel Okafor · Chargeback analyst

    The agents finished the overnight run at 06:40: 61 disputes in from three processors, 44 packs drafted and checked, 12 proposed to accept. Today shows 412 open disputes with $171,860 at stake, 23 due in the next 3 days with 21 packs ready, and a Q3 win rate of 62%, up from 41%. At the top of his list: CB-88213 qualifies for Compelling Evidence 3.0.

    Intake agent: “Brought in 61 disputes: Northbeam 44, Halberd 11, Ridgeway 6. Every deadline set to the processor's date.”

  2. 02Open the dispute

    The reason code becomes a list of evidence to fill

    Evidence agent

    CB-88213 is a Visa 10.4 Other Fraud — Card-Absent Environment claim from J. Pell, card ending 4417, on order KVH-4471902. Northbeam wants the response by Sat 17 Oct; the network date is Thu 22 Oct. Priced as a plain fraud claim, the win odds are 31%: 31% × $612.40 − $22 to fight = $167.84. The left side lists a socket for every piece of evidence the rule requires, and the agent fills them as he watches.

    “Evidence agent · step 5 of 9 · Matched the device on all three.”

  3. 03Every exhibit

    Two earlier orders, the same device and IP address

    Evidence agent

    The agent pulls the disputed order, the Corvid Parcel delivery with a photo at the front door on Wed 5 Aug, and a verified sign-in with a code to the account holder's phone six minutes before the order. Then it searches 12 months of the card and finds KVH-4012277, 140 days earlier, and KVH-3768410, 301 days earlier — neither disputed, both from device dv-7f3a-91c2 and IP address 198.51.100.24. Every exhibit opens its source record.

    “Highlighted fields are the ones the agents relied on. Read-only copy of the record, taken when the agent read it.”

  4. 04Qualified

    Win odds from 31% to 78%

    Triage agent

    Nine of nine sockets are filled with eight exhibits, and the Compelling Evidence 3.0 test passes: two earlier orders 120–365 days old, neither disputed nor reported as fraud, the device, IP address and shipping address matching on all three (the rule needs two of four, one of them the device or IP address), same merchant and descriptor. The triage agent re-prices the dispute at 78%: $455.67 expected if he fights, against a $612.40 refund and a $2.00 fee if he accepts.

    The evidence agent never invents an exhibit — an empty socket stays empty.

  5. 05Before he signs

    A critic reads it as the issuer would, and he asks why

    Critic agent · Daniel Okafor

    The drafting agent wrote the response with every sentence pointing at an exhibit. The critic scored it 86 against a pass mark of 75, struck a sentence about the three-year warranty and moved the match table to page 1. Daniel asks why the dispute qualifies; the evidence agent answers with the two orders, the matching device and IP address and the rule, each cited.

    Critic: “irrelevant to a fraud claim, and it invites a quality argument.”

  6. 06Signed, three days early

    He submits with a reason code and his e-signature

    Daniel Okafor · Chargeback analyst

    Daniel picks reason code S1 · Evidence complete — Compelling Evidence 3.0, adds a note if he wants one, and approves with his e-signature. The response goes to Northbeam three days before its deadline. Had the critic scored it below 75, he could only have submitted it with reason S3 and a reason in his own words.

    “I approve this as Daniel Okafor, Chargeback Analyst — e-signature.”

  7. 07One step

    Twelve weak disputes accepted, each with its arithmetic

    Triage agent

    The triage agent proposes accepting 12 disputes worth $1,485.35: four are Kestrel & Vane's own mistakes — a duplicate capture, a missed cancellation, a forced authorisation and a return never refunded — two look like true fraud, and six cost more to fight than they could recover. Daniel can switch any row to Fight instead, then approves the rest with one reason code inside the free window.

    “8% × $459.05 − $22 = $14.72 — below your $15 fight floor.”

  8. 08Pre-arbitration

    Round two, priced against a third way out

    Triage agent

    On CB-87455 the issuer comes back with photos of a dented door and a $640 repair quote. The triage agent prices every option: escalating to arbitration is worth about $36 after the filing fee, accepting alone costs $1,960.00, and accepting while filing a concealed-damage claim with Trident Freight recovers about $1,568. Daniel chooses; the evidence agent has the claim drafted.

  9. 09Prevention

    Repeat disputers stepped up at checkout, not fought one by one

    Rafael Montes · Fraud analyst

    The pattern agent finds 14 repeat disputers this year, $9,820.00 across 33 disputes, and proposes a change for each of the 6 new ones — mostly step-up verification at checkout. It also sees Visa 10.4 up 18% at KV Home Store since the garden promotion, and a descriptor customers do not recognise. Rafael approves or declines each proposal with his signature.

    “Nobody is blocked: step-up asks for a code at checkout.”

  10. 10Month end

    A win counts when the money is back

    Helen Achterberg · Finance controller

    The outcomes agent matches every recovery to a processor settlement line: $679,400 won in Q3, $671,950 matched, and $7,450 across three items not yet matched, each one explained. It proposes a reserve for open disputes of $74,438.16 — open amount × (1 − weighted win odds) — and journal JV-CB-1014. Helen approves the journal; the agent never posts it.

Who it’s for

Built for everyone who touches a dispute.

The same disputes, seen by the five people who carry them — what their week looked like, and what it looks like now, in their own words.

DO
Daniel OkaforChargeback analyst, payments operations · about 60 new disputes a day
Chargeback analyst
Before
Decided by feel which disputes to fight, then searched five systems and pasted exhibits into a template in the last two days of the window.
Now
“Tell me which ones are worth fighting, and show me the proof before I sign” — he opens a pack already filled, checked and priced, and decides.
IS
Ingrid SolbergPayments operations manager · co-signs above $2,000
Payments operations manager
Before
Reported the win rate monthly without knowing why disputes were lost, and found out about expired ones afterwards.
Now
“I want to know we never let one expire, and that we stopped fighting the ones we always lose” — she sets the thresholds, co-signs large submissions and sees the losing socket per reason code.
RM
Rafael MontesFraud analyst · approves prevention
Fraud analyst
Before
Saw the same accounts dispute every quarter, fought one dispute at a time.
Now
“If the same people dispute every quarter, I want them stepped up at checkout” — he approves each proposal from the pattern agent with his signature.
HA
Helen AchterbergFinance controller · recoveries and the month-end reserve
Finance controller
Before
Reconciled processor settlement files to wins by hand and set the chargeback reserve on a rule of thumb.
Now
“A win is only a win when the money is back in our account” — she approves a reserve built on the same win odds every dispute shows.
PN
Priya NairInternal audit · read-only
Internal audit
Before
Sampled disputes each quarter by asking the team who decided what, and on which evidence.
Now
“Show me who decided, on what evidence, and when” — she filters the trail by person or agent and exports the evidence for any dispute.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents price every dispute, fill the evidence the reason code requires and check each other's work; the analyst decides and signs.

Intake agent

Brings every dispute, pre-dispute alert and pre-arbitration in from each processor every 15 minutes, maps the reason code to its playbook, and sets the due date to the processor's date with the network's date beside it.

  • Never changes a deadline
  • Never responds to a processor
Triage agent

Prices every dispute from 12 months of your own outcomes for the same reason code and business — win odds × amount − cost to fight — and proposes fight, accept, refund through an alert, or recover elsewhere. It re-prices whenever the evidence changes.

  • Proposals only — a person accepts
  • Shows the arithmetic on every proposal
Evidence agent

Plans which systems answer each socket, fills the required ones first with cited exhibits, and for every Visa 10.4 searches 12 months of the card for two undisputed orders 120–365 days old and tests the matching elements for Compelling Evidence 3.0.

  • Read-only
  • Never invents an exhibit — an empty socket stays empty
  • Never contacts a cardholder
Drafting agent

Writes the response for the reason code, leading with the strongest path and pointing every sentence at an exhibit — one page plus exhibits.

  • No argument beyond the evidence
  • Plain language, no threats
Critic agent

Reads every pack as the issuer's reviewer would, scores it against the reason code, strikes what does not help, and sends weak packs back to the evidence agent with the missing socket named.

  • Cannot submit
  • Cannot lower the pass mark
  • Strikes shown as tracked changes
Pattern agent

Finds repeat disputers, reason codes on the rise and descriptors customers do not recognise, and proposes prevention to the fraud analyst.

  • Proposes only — never blocks a customer
  • Accounts, never card numbers
Outcomes agent

Records wins and losses, matches every recovery to a settlement line and the ledger, explains every unmatched item, computes the reserve and win rates, and watches the dispute ratio per account.

  • Never posts a journal
  • Never closes a dispute without the processor's outcome
Chargeback analyst

Signs every submission and acceptance; the operations manager co-signs above $2,000. The agents propose; a named person decides.

Ask in plain words

Ask the agents about any dispute, in plain words

Every screen has the agents in reach. Ask why, what if, or what to do next — they answer with the records behind each claim, and nothing is submitted, accepted or refunded until a person approves it.

Why does it qualify for Compelling Evidence 3.0?

Two earlier orders on the same card fall inside the 120–365-day window: KVH-4012277, 140 days before, and KVH-3768410, 301 days before. Neither was disputed or reported as fraud. All three share device ID dv-7f3a-91c2 and IP address 198.51.100.24 — two matching elements, one of them the device. Same merchant and descriptor. That meets the rule, which shifts liability back to the issuer.

What if we accept instead?

Accepting returns nothing and costs a $2.00 acceptance fee — we are on day 22 of 30. Fighting: 78% × $612.40 − $22 to fight = $455.67 expected. Before the Compelling Evidence 3.0 search it was 31% and $167.84. Fight.

Why accept CB-88299? It is $459.05

Checkout risk scored the order 91 / 100 and it shipped on a manual override to a different state from the billing address. Two of our last three disputes like this were lost; win odds 8%. 8% × $459.05 − $22 = $14.72 — below your $15 fight floor. I passed the override to Rafael Montes.

Did any agent act without a person?

Only under the alert refund rule Ingrid Solberg set: 31 refunds this week, each under $25 on an unshipped order, each logged with the rule version. Every submission, acceptance, pre-arbitration answer and journal carries a person's reason code and e-signature.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

TodayWhat the agents did overnight, the four numbers that matter, the decisions waiting for the analyst and a conversation with the agents.
Agents at work on a disputeThe reason code's required evidence on the left, the evidence pack filling on the right, each step in view — with a button to stop the agent.
One dispute, one pageWin odds, the processor's deadline and the network's, the value of fighting against accepting, every socket filled and every exhibit with its source.
The record behind an exhibitA read-only copy of the source record, with the fields the agents relied on highlighted.
Response, critic and questionsThe drafted response with the critic's strike shown as a tracked change, the Compelling Evidence 3.0 test, and the agents answering why, with sources.
Submit with a reason codeThe reason code, a note for the record and the analyst's e-signature before the response goes to the processor.
Fight or acceptEvery proposal to accept with its reason and arithmetic — win odds × amount − cost to fight — and Fight instead on every row.
Pre-arbitrationWhat the issuer says now, what we have, and every option priced — including a claim against the carrier.
Patterns and preventionRepeat disputers, reason codes on the rise and an unrecognised descriptor, each with a proposal for the fraud analyst to approve or decline.
ResultsWin rate by month, recovered, fought by value, expired, the dispute ratio per account against the network threshold, and where each reason code is lost.
MoneyRecoveries matched to settlement lines, each unmatched item explained, the reserve for open disputes and the proposed journal.
Audit trailEvery agent step and every person's decision in order, with reason codes and signatures, a chain anyone can verify and an evidence export per dispute.
Your rulesFight floor, cost to fight, critic pass mark, co-sign limit, lead time, alert refund rule, pre-arbitration threshold and data retention — versioned.
Governance

Built for scrutiny: cited, signed, on the record.

Every exhibit opens its sourceEach exhibit and each answer from the agents links to the record it came from — the order, the carrier scan, the sign-in, the device — with the fields relied on highlighted. Nothing is submitted that is not in a socket.
A person decides, with a reason codeEvery submission, acceptance, pre-arbitration answer and journal needs a person's reason code and e-signature. Above $2,000 the payments operations manager co-signs, and the submitter cannot co-sign.
A critic before the issuerThe critic must pass a pack at the pass mark — 75 by default — or the analyst overrides it with reason S3 and says why. Packs it sends back go to the evidence agent with the missing evidence named.
What the agents may not doAgents never submit, accept, refund, contact a cardholder, change a deadline, post a journal or block a customer. The only automatic refunds are pre-dispute alerts under the manager's own rule, each one logged.
A trail nobody can changeEvery agent step and every person's decision is on a hash-chained audit trail, with its reason code and signature. Anyone with access can verify the chain and export the evidence for any dispute.
Card data kept to its purposeCard numbers are masked to the last four. Device and IP data are used for disputes only and deleted after the retention period, 18 months by default.
Configuration

Your dispute policy, not ours

The thresholds the agents work within are settings. Every change is versioned and on the audit trail — like Ingrid Solberg raising the critic pass mark from 70 to 75.

SettingDefaultChoose from
Fight floor$15Propose to fight only when win odds × amount − cost to fight is above it
Cost to fight one dispute$22Analyst minutes and processor fee, used in every expected value
Critic pass mark75 / 100A pack below it goes only with an override and reason S3
Co-sign above$2,000Submissions above it need the payments operations manager
Submit lead time2 daysPacks are ready this many days before the processor's due date
Alert refund rule$25Pre-dispute alerts refunded automatically up to it when the order has not shipped
Escalate pre-arbitration only when$100Expected value after the filing fee is above it
Keep device and IP data for disputes18 monthsThen deleted; used for nothing else
Connections

Works with the systems a dispute already lives in

Card processorsdisputes, pre-dispute alerts, pre-arbitrations and settlement files, from several processors at once
Order managementorders, items, refunds and descriptors
Carrier trackingscans, delivery photos and signatures
Customer accounts and devicessign-in log, verification codes, device IDs, IP addresses and checkout risk scores
Service desk and subscription billingchats, e-mails and tickets; plans, renewals and cancellations
General ledgerrecoveries matched line by line; reserve journals proposed for approval
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

estimated
$1.55M
more recovered a year: more of the right disputes fought, and more of them won
Fought 48%, won 41%$1.17M
Fought 74%, won 62%$2.72M
target
0expired
disputes left to expire; dispute ratio held under the 1.5% network threshold
0.61% of 1.5%
busiest account, September
target
1day
from dispute to a cited, critic-checked pack, not the last two days of the window
By hand≈ 17 days
With agents≈ 1 day

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate ($1.55M = $5.92M disputed a year at the fictional group, fought share 48% → 74% and win rate 41% → 62%; the split of days is estimated too) · “typical” = published figures (Mastercard 2025 global chargebacks outlook — 324 million chargebacks a year by 2028, 45% reported by merchants as fraud; LexisNexis Risk Solutions True Cost of Fraud 2025 — $4.61 per $1 of fraud, US). Visa Compelling Evidence 3.0 and the network dispute-ratio threshold are paraphrased. People, companies, processors, carriers and cardholders named on this page are fictional — characters and sample data in the working solution.

Questions

What payments and finance teams ask us.

What is chargeback management software?

Software that takes a card dispute from the processor's notice to a decision: fight it with a representment response, accept it, or prevent the next one. Chargeback Management adds seven agents that bring every dispute in with its true deadline, price fight or accept, fill the evidence the reason code requires, draft the response and check it as the issuer would — while the chargeback analyst decides and signs.

How does it decide which chargebacks to fight?

The triage agent prices every dispute from 12 months of your own outcomes for the same reason code and business: win odds × amount − the cost to fight. When that is below your fight floor it proposes accepting, with the reason and the arithmetic on the row. It only proposes; the analyst approves, or switches any row to fight instead.

How does it handle friendly fraud and Compelling Evidence 3.0?

On every Visa 10.4 fraud claim the evidence agent searches 12 months of the card for two earlier undisputed orders 120–365 days old and tests whether at least two of four elements match, one of them the IP address or device, with the same merchant and descriptor. When the test passes, the response is built on it — in the demo, win odds rose from 31% to 78%.

Does the AI submit responses or refund customers on its own?

No. Agents never submit, accept, refund, contact a cardholder, change a deadline, post a journal or block a customer. Every submission and acceptance carries the analyst's reason code and e-signature, and the payments operations manager co-signs above $2,000. The one exception is a pre-dispute alert refund under a rule the manager sets, logged each time.

Can it work with several processors and card networks?

Yes. The intake agent reads disputes, alerts and pre-arbitrations from each processor every 15 minutes and sets each due date to the processor's own date, with the network's date beside it. Reason codes from Visa, Mastercard, American Express and Discover each have a playbook of the evidence they require, which your team can edit.

What does finance get from it?

The outcomes agent matches every win to a processor settlement line and the ledger and explains anything unmatched. It proposes the month-end reserve for open disputes — open amount × (1 − weighted win odds), by business — and the journal, which the finance controller approves; the agent never posts it.

Can we set our own thresholds and rules?

Yes. The fight floor, the cost to fight, the critic pass mark, the co-sign limit, the submit lead time, the alert refund rule, the pre-arbitration threshold and how long device and IP data are kept are all settings, versioned and on the audit trail.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your dispute policy, processor connections and 12 months of dispute history for the baseline — and it goes live once every quality gate has passed. We will walk you through it on your own past disputes first.

See it on
your disputes.

We'll run Chargeback Management on a sample of your own past disputes and the systems their evidence lives in.