Chargeback Management Software for ISOs

If you run an ISO, a payfac or a software company that has taken payments in-house, we think chargeback management software solves only part of your problem. Chargeback management software is the tooling a merchant uses to track disputes, assemble evidence and submit representments to win chargebacks back. It helps a merchant defend its own disputes, while your harder job is managing loss across a whole portfolio of sub-merchants.

The useful question is not only which chargebacks you won. It is which merchants are moving your portfolio ratio, what that ratio will look like next month and what you should do before you cross a threshold.

No merchant-side dispute tool answers that on its own. This post covers who ends up liable for a chargeback, how merchant and portfolio monitoring differ, why the portfolio ratio is harder to own than it looks, the decisions that move it, what to buy and build and a one-week diagnostic you can run with files you already have.

How Chargeback Liability Moves Up the Payment Chain

For operators, the cleanest way to think about chargeback liability is as a chain. A failed dispute moves through the parties that signed up for the merchant, and we find the party holding the indemnity is usually the one left with the loss:

1. The cardholder disputes the transaction.
2. The issuer, the cardholder's bank, opens and evaluates the dispute.
3. The network, such as Visa or Mastercard, sets the rules and runs the settlement process.
4. The acquirer, the merchant's acquiring bank or processor, sits contractually upstream of the merchant.
5. The ISO, payfac or platform underwrote the merchant and often agrees to cover losses, reserves or chargeback exposure.
6. The sub-merchant generated the original sale.

In ordinary language, people say the merchant eats the chargeback. That is true until the merchant cannot, because if the sub-merchant fails, disappears or cannot reimburse the loss, the liability moves to whoever guaranteed the merchant relationship, which for an ISO or payfac is often you.

So the consumer answer to liability is simple, while the operator answer depends on the contract, the reserve structure and where indemnity sits in the merchant agreement.

Merchant-Level and Portfolio-Level Monitoring Compared

Most chargeback tools are built around a single merchant and its MID, the merchant identification used by processors and acquirers. We see them track disputes, evidence, deadlines and representment well, which is exactly what a merchant needs and not what a portfolio owner needs.

For an ISO or payfac, the real question is if the whole portfolio is drifting toward a monitoring threshold. Visa says its evolved Visa Acquirer Monitoring Program, effective April 1, 2025, consolidates five existing fraud and dispute programs into a single acquirer program and reduces 38 distinct remediation processes to one. Visa's own rules or your acquirer's bulletin should be the source for any current threshold, because numbers and effective dates change.

Mastercard's excessive chargeback programs create a similar operator problem, even though the details differ. The point is the same, which is that if the consequence sits above the merchant, your monitoring has to sit above the merchant too.

Why Your Portfolio Ratio Is Not a Number You Already Own

An acquirer portal can show you a ratio, but that does not make it your ratio. It is computed from that acquirer's view of the world, on its schedule, using its merchant identifiers and filing conventions, and we rarely see two acquirers agree on the details.

Portfolio truth is messy because the data arrives fragmented. Fraud reports and chargeback records come in different files from different acquirers with different lag times, the same sub-merchant may appear under more than one MID, merchants move between processors mid-year and some records arrive after the month you need to act on has closed.

To trust a portfolio ratio, you need one merchant dimension across all of those feeds. That means normalizing identifiers, mapping MIDs back to the economic merchant you underwrote and deciding how to treat merchants that changed processors, legal entities or verticals. This is not a dashboard problem but a ledger problem.

Bank supervisors have expected this kind of monitoring for a long time. The OCC told banks that their risk management program should include procedures for monitoring processor information such as merchant data, transaction volume, and charge-back history, and the FDIC's guidance says institutions should implement systems to monitor for higher rates of returns or charge backs. Your sponsor bank will care about that number, not about how clean your internal spreadsheet was.

The Decisions That Actually Move the Portfolio Ratio

The decisions that move a portfolio ratio happen before the monthly report closes, so watching only the dispute queue means acting too late. We group them into five decisions, each with its own time horizon.

1. Decide What You Will Board and on What Terms

At underwriting, you decide what you will accept, at what reserve and at what price. A merchant with thin margins, high refund rates, delayed fulfillment or poor dispute history may still be worth boarding, but only with tighter controls.

If those decisions live in an underwriter's head rather than in rules and records, you are underwriting by memory. Encoding them also makes it possible to see later which underwriting choices produced the merchants that now drive the ratio.

2. Size Reserves to the Exposure You Carry

Reserves are how you turn a merchant's future chargeback risk into money you hold today. Size them by expected dispute and refund exposure, delivery delay and the merchant's own history, not by a single default percentage for everyone.

A reserve ledger should show what exposure is covered, by whom and until when. Without it, a merchant can leave with the reserve released while disputes from its last months of sales are still arriving.

3. Apply In-Life Controls Tied to Early Signals

Once a merchant is live, you can still change the shape of the loss. Velocity caps, delivery-delay monitoring, reserve step-ups, refund scrutiny and review of descriptor changes can all reduce future dispute load.

These controls only work if they are triggered by signals that predict loss early enough to matter, which usually means weekly or daily data rather than the monthly acquirer report.

4. Forecast the Ratio From Partial-Month Data

A merchant can look acceptable on its own while the portfolio moves toward a sponsor-level problem. Forecasting the ratio from partial-month data, adjusted for known reporting lags, shows where the month is heading while there is still time to act.

The forecast does not need to be sophisticated to be useful. A simple projection from the first weeks of the month, broken down by merchant, already tells you which few merchants to call before month end.

5. Exit Merchants Before the Ratio Is Breached

Offboarding is the hardest decision and often the most expensive one to delay. If a merchant is clearly pushing the portfolio toward a threshold and the economics do not justify the exposure, late exit costs more than early exit.

By the time the ratio is breached, the sponsor bank has more leverage than you do. An offboarding workflow with an audit trail turns exit into a deliberate risk decision rather than a rushed operations task.

What to Buy and What to Build for Portfolio Risk

The simplest rule is to buy commodity chargeback dispute work and build portfolio risk control. We find that is where the line usually falls for an ISO or payfac.

Do not build everything. With a small book of sub-merchants, a single acquirer and no meaningful reserve program, a portfolio model may be premature, and a strong dispute tool plus disciplined manual review may be enough. Build once you have more than one acquirer, enough merchants that one bad actor can move the ratio and a liability structure that makes the book's loss your problem.

The build side is classic fintech software development, normalizing many feeds into one trustworthy ledger and deciding from it. The same shape appears in Nacha fraud monitoring for operators, in factoring portfolio risk and in trade reconciliation.

A One-Week Diagnostic Before You Spend Anything

To find out if you have a portfolio problem, we would reconstruct the last twelve months from files you already receive. Start with acquirer dispute reports, fraud files, settlement or reversal records and your internal merchant master, map every record to one merchant dimension, then group by month, merchant and merchant category code.

From there, answer four questions:

• Which merchants contribute the most to disputes and fraud combined?
• Which merchants are trending worse this month than in prior months?
• Which acquirer feeds are lagging, incomplete or using inconsistent identifiers?
• What would happen to the portfolio ratio if the top one or two merchants continued at the current pace?

If you cannot answer those questions quickly, the problem is not your chargeback queue but your ledger and risk model. That is the point at which single-merchant chargeback tools stop being the right category.

Buy Chargeback Management Software and Own the Portfolio View

Chargeback management software is still useful for the merchant-side workflow of disputes, evidence, deadlines and representment, but for an ISO or payfac it is necessary rather than sufficient. The real requirement is a portfolio view that normalizes data from multiple acquirers, rolls it into one merchant dimension, forecasts the ratio before month end and drives underwriting, reserve and exit decisions.

We have seen the same pattern in our financial services work, including transaction and reconciliation systems for UTR8, AllOptions and Valon. The sector differs, but the underlying problem is the same, and the team at Better Software can help you scope the portfolio layer.

Frequently Asked Questions

What Is Chargeback Management?

Chargeback management is the work of preventing, tracking and disputing chargebacks, from alerts and refunds before a dispute to evidence and representment after it. We treat it as two jobs for payment companies, case handling for each merchant and risk control across the whole portfolio.

Do Companies Get Charged for Chargebacks?

Yes, merchants usually lose the disputed amount if they do not win, and acquirers or processors often add a chargeback fee. We also see programs charge further fees when ratios stay high, and an ISO or payfac may absorb losses a failed merchant cannot cover.

What Are Chargeback Rights?

Chargeback rights are the protections that let a cardholder dispute a card transaction through the issuing bank, for reasons such as fraud or goods not received. We remind operators that merchants have matching rights to respond with evidence through representment under network rules.

How Often Do Chargebacks Happen?

It varies widely by merchant category, fulfillment model and fraud exposure, so there is no single rate. We measure it as a ratio per merchant and across the portfolio every month, and compare it with the thresholds in the network programs and the acquirer agreement.

Can a Company Dispute a Chargeback?

Yes, a merchant can dispute a chargeback through representment, submitting evidence such as delivery proof, authorization records or terms the cardholder accepted. We recommend buying good tooling for this repeatable work and keeping internal engineering effort for the portfolio risk decisions only you can make.