Why dispute management is overdue for an overhaul

For decades, the payments industry has treated disputes as an unavoidable cost of doing business.

A customer clicks a button, a chargeback appears, and the process starts moving through a maze of issuers, acquirers, card networks, and merchants. Each party works inside its own system, with its own data, timelines, and incentives. The outcome is a dispute process rife with inconsistencies, inconvenience, inefficiencies and injustice for merchants.

The infrastructure behind disputes still looks like it did decades ago. Email threads, manual case handling, siloed databases, and workflows that rely more on habit than logic. Meanwhile, payments themselves have moved on. We now have instant transfers, embedded finance, digital currencies and digital wallets that transact in seconds.

Disputes, on the other hand, can take weeks or months to resolve. That gap is starting to feel impossible to ignore.

The next step is obvious. If payments are becoming real-time, borderless, and API-driven, dispute management has to follow the same path.

Today, when a customer files a dispute, the data often gets copied, translated, and passed through multiple systems before it reaches the merchant. Evidence then travels back along the same path. At every step, something can get lost, delayed, or misinterpreted.

The process is fragmented because the infrastructure is fragmented. Each stakeholder runs its own tools, keeps its own records, and follows its own workflow. There is no shared environment where everyone works from the same case data. That structure made sense when payments were slower, more local, and largely card based. It makes less sense in a world of instant payments, open banking, and global e-commerce.

So the question is not whether this model will change, but how?

The next phase of dispute management is likely to look very different. Instead of separate systems connected by file transfers and manual steps, the industry is starting to explore shared platforms, real-time data exchange, and automation across the entire dispute lifecycle. Think of it less like a collection of tools, and more like a common operating environment for disputes.

In this model, issuers, acquirers, fintechs, and merchants would all work from the same case data. Evidence would not need to be copied from one system to another. Decisions could happen faster because everyone is looking at the same information at the same time.

We have seen this pattern before. Fraud management moved from isolated rule engines to shared intelligence networks. Open banking turned account data into a platform rather than a closed asset. Real-time payments forced banks to rethink settlement, liquidity, and risk in new ways.

Disputes are simply the next piece of the puzzle.

Of course, the hard part is not the technology. It is coordination. Disputes involve multiple parties, each with their own commercial incentives, regulatory duties, and legacy systems. A shared model only works if enough of those players decide the old process is no longer worth the friction.

But the pressure is building. Customers expect instant answers. Merchants want faster, fairer outcomes at lower costs. Issuers are dealing with rising dispute volumes across more payment types than ever before.

The current model was designed for a slower, simpler payments world. That world no longer exists. Now, the real question is not whether disputes will change, it is who will take the first step toward a model that matches the speed and structure of modern payments.