Executive Summary

On April 22, 2026, three New York merchants filed a lawsuit against Visa and Mastercard in the Southern District of New York, simultaneously requesting summary judgment from U.S. District Judge Brian Cogan in Brooklyn to remove the legal immunity provision embedded in the 2019 antitrust class-action settlement. That settlement provided approximately $6 billion in damages to an estimated 15 million U.S. merchants covering a 15-year class period through early 2019, but included a provision shielding the networks from future claims for conduct after the settlement period.

The new complaint argues this immunity functions as an illegal license to continue anticompetitive behavior, seeking damages for card fees paid since January 2019. For financial system architects, this is not merely a legal dispute—it is a structural challenge to the settlement mechanics and interchange fee architecture that underpin the four-party card network model. The 2019 settlement effectively monetized legal risk while preserving the networks’ fee-setting authority and routing rules.

If the immunity provision is removed, the architectural implications are significant: interchange fee calculation engines, batch clearing processes, and network routing rules would face renewed legal and economic pressure. This case exposes the tension between settlement finality—a core architectural principle for balancing ledgers between issuers and acquirers—and the continuous evolution of payment system design. The outcome could force fundamental reconfiguration of how settlement economics are encoded into payment infrastructure.

What Happened

On April 22, 2026, three New York merchants filed a lawsuit against Visa and Mastercard in the U.S. District Court for the Southern District of New York. Simultaneously, they requested a summary judgment from U.S. District Judge Brian Cogan in Brooklyn, who retains jurisdiction over the 2019 class-action settlement that the merchants now seek to unwind.

The 2019 settlement provided approximately $6 billion in damages to an estimated 15 million U.S. merchants for a 15-year class period ending in early 2019. Critically, that settlement included a provision granting Visa and Mastercard legal immunity from future claims based on conduct occurring after the settlement period. The new lawsuit argues this immunity constitutes an illegal license to continue anticompetitive behavior, seeking damages for card fees paid since January 2019.

From an architectural perspective, this is not merely a legal dispute over past fees. It is a challenge to the settlement mechanism itself—the legal equivalent of a system that finalizes a batch settlement while allowing the counterparty to continue operating under the same rules without further reconciliation. The merchants are asking the court to reopen the settlement window, forcing the networks to defend their ongoing fee structures on the merits.

Why It Matters

This lawsuit against Visa and Mastercard transcends the immediate headlines. It challenges the fundamental legal and economic model underpinning the four-party card network, specifically questioning whether settlement immunity can perpetually shield ongoing architectural decisions regarding interchange fees and network rules.

If the plaintiffs succeed, Visa and Mastercard could be compelled to redesign their interchange fee structures, settlement rules, and network access policies. This isn’t merely about tweaking numbers; it’s about potentially re-architecting core components of the payment system. The case exposes the inherent tension between achieving finality in legal settlements and the continuous evolution of payment system architecture. Can a past agreement truly bind future architectural choices, especially when those choices are alleged to perpetuate anti-competitive behavior?

For financial system architects, this lawsuit presents a live case study in how legal frameworks constrain or enable technical and economic design choices. It highlights the importance of designing payment systems with an awareness of the legal landscape and the potential for future challenges to existing norms. The outcome could significantly influence how we think about the long-term governance and evolution of payment networks.

Business Model View

The 2019 settlement created an unusual architectural pattern in the payment industry: a legal safe harbor that allowed Visa and Mastercard to maintain their fee structures while paying a one-time damages pool of approximately $6 billion. From a business model perspective, this was a rational trade—monetize legal risk rather than redesign the economic engine.

Visa and Mastercard’s revenue model depends on two primary streams: service fees (tied to transaction volume) and data processing fees (tied to message count). Both are structurally linked to interchange rates, which the networks set and which flow from acquirers to issuers. Merchants bear the cost, making interchange the core of the antitrust complaint.

The new lawsuit challenges whether settlement immunity can shield ongoing architectural decisions. If the safe harbor is removed, the networks face a fundamentally different risk profile: rolling damages for each year of alleged overcharging since January 2019, rather than a single capped settlement.

For payment architects, this exposes a critical design tension. The 2019 settlement allowed the networks to treat legal risk as a fixed cost rather than a variable one tied to system behavior. The new suit argues that this is an illegal license to continue anticompetitive conduct. The architectural implication is clear: fee calculation engines, interchange schedules, and network routing rules were designed under the assumption of legal finality. That assumption is now contested.

The outcome will determine whether payment networks can continue to treat legal settlements as architectural constraints or must redesign their economic models to withstand ongoing scrutiny.

Payment Landscape View

This lawsuit does not exist in isolation. It enters a payment landscape already under structural pressure from three directions: regulation, alternative rails, and merchant-led economic renegotiation.

Regulatory scrutiny is intensifying globally. In the US, the Durbin Amendment already caps debit interchange for large issuers, and the CFPB’s focus on “junk fees” creates a regulatory tailwind for merchant arguments. In Europe, PSD2 and the Interchange Fee Regulation have capped consumer card fees and opened the door to third-party access. This lawsuit extends the same logic—challenging whether network-set fees can persist without antitrust exposure—into the US credit card market, which has largely escaped such caps.

Alternative payment rails are eroding the network duopoly’s structural moat. FedNow and RTP offer real-time settlement without card network intermediation. BNPL providers and account-to-account schemes (e.g., Pay by Bank) compete on cost and speed. If this lawsuit weakens Visa and Mastercard’s legal immunity, it may accelerate merchant adoption of these alternatives, shifting transaction volume away from card rails.

Merchant coalitions are increasingly sophisticated. Large retailers and trade groups now use legal strategy as a design tool—filing suits not just for damages but to force architectural changes in routing rules, fee disclosure, and settlement timing. This lawsuit is one front in a coordinated campaign.

For payment architects, the landscape implication is clear: the four-party model’s legal and economic defenses are thinning. New architectures—open banking, tokenized networks, real-time rails—should be designed with the assumption that interchange-style fee models will face continued legal challenge. Building modular fee and routing logic today reduces rework when the landscape shifts.

Payment Architecture View

From an architectural standpoint, this lawsuit targets four interconnected layers of the card payment system: settlement finality, clearing mechanics, interchange calculation engines, and network routing rules.

Settlement finality is the architectural guarantee that once net positions are calculated and funds transferred, the transaction is complete. The 2019 settlement granted Visa and Mastercard a form of legal settlement finality—immunity from future claims for conduct after the settlement period. The new suit argues this immunity is architecturally unsound: it decouples legal finality from the ongoing economic flows that settlement systems process daily. If the court agrees, the settlement layer loses its safe harbor, meaning every batch settlement run becomes a potential evidence point in future litigation.

Clearing systems are the batch processes that calculate net positions between issuers and acquirers. These systems compute interchange fees per transaction using rate tables published by the networks. The lawsuit alleges these calculations systematically overcharge merchants. From an architecture perspective, clearing engines are deterministic: given a transaction and a rate table, they produce a fee. The legal question is whether the rate tables themselves are anticompetitive. If the answer is yes, clearing systems must be redesigned to support alternative fee models—potentially multiple concurrent rate tables for different merchant classes or routing paths.

Interchange calculation is not a single formula but a complex rule set with hundreds of rate categories based on card type, transaction method, merchant category code, and authorization data. The architectural challenge is that these rules are embedded in acquirer and network systems, often in proprietary formats. Changing them requires coordinated updates across thousands of endpoints.

Network routing rules prevent merchants from steering transactions to lower-cost networks. Architecturally, this means routing logic in payment gateways and acquirer systems is constrained by network agreements, not technical capability. A successful lawsuit could force routing flexibility, requiring token vaults and switch logic to support dynamic, cost-based routing decisions.

Technical Breakdown

The lawsuit’s focus on settlement economics—not authorization logic—means the most immediate architectural impact lands on clearing and settlement systems, not the real-time transaction path. Authorization remains the domain of issuer risk decisions and network routing rules; the contested ground is what happens after the transaction is approved.

Fee calculation engines are the primary systems at risk. Acquirers and networks operate batch processes that compute interchange fees per transaction based on complex rate tables, merchant category codes, transaction amounts, and card product tiers. If the lawsuit succeeds in reopening interchange rate structures, these engines would require reconfiguration—potentially supporting multiple fee models simultaneously during a transition period. The clearing files (typically ISO 8583 or ISO 20022 messages) carry the fee data that flows into merchant settlement amounts.

Reconciliation workflows face disruption from two directions. First, if fee structures change, merchants and acquirers must adjust their internal reconciliation logic to match new expected costs against actual settlement amounts. Second, if the court orders retroactive adjustments—a plausible but uncertain outcome—reconciliation systems must handle large-scale recalculations across historical transaction batches, a non-trivial operational challenge given batch boundaries and cut-off times.

Tokenization and routing become architectural concerns only if the lawsuit successfully challenges network routing rules. Currently, Visa and Mastercard enforce rules preventing merchants from routing tokenized transactions to lower-cost networks. If those rules fall, token vaults and network routing logic must support dynamic selection of alternative rails. This implies architectural changes to token domain controls and fallback behavior.

The core architectural lesson: settlement systems designed for static fee models lack the flexibility to absorb legal-driven recalibrations. Builders should audit their clearing pipelines for hardcoded fee logic and batch immutability constraints.

Risk and Reliability Considerations

For payment architects, this lawsuit introduces a class of risk that is rarely modeled in system design: legal retroactivity applied to settlement economics. The core reliability concern is not whether the networks will fail to settle—they will not—but whether the settlement parameters can shift underfoot.

If the court grants summary judgment and removes the 2019 settlement’s immunity provision, the networks face potential liability for interchange fees collected since January 2019. This creates a scenario where settlement systems must support retroactive fee recalculations across millions of merchants and billions of transactions. Most clearing engines are designed for forward-looking rule changes, not backward-looking adjustments that require replaying historical batches with new fee schedules. The operational strain on reconciliation workflows—matching recalculated net positions against already-settled funds—could cascade into settlement delays or disputed balances.

Legal uncertainty itself introduces a reliability risk: networks may defer infrastructure upgrades (e.g., ISO 20022 migration, token vault modernization) while litigation outcomes are unclear. This slows the evolution of the payment architecture at a time when real-time rails and open banking are accelerating.

Merchants face cash flow volatility if fee structures change unpredictably. A merchant’s payment acceptance strategy—routing decisions, surcharging policies, acceptance of specific card products—is built on predictable interchange costs. Sudden shifts force renegotiation of acquirer contracts and reconfiguration of point-of-sale systems.

Finally, fragmented legal outcomes across jurisdictions (U.S. federal courts, EU competition authorities, emerging-market regulators) could force architects to maintain multi-rail settlement logic that adapts fee models per region. This increases system complexity and testing burden. The most resilient architectures will treat fee schedules as external, versioned parameters—not hardcoded business logic—so that legal shocks can be absorbed without rewiring core settlement engines.

What Builders Should Watch

For payment architects and fintech builders, this lawsuit introduces a new vector of legal uncertainty into systems that depend on stable settlement economics. Here is what to monitor and how to prepare.

Monitor the legal signal. The summary judgment decision from Judge Cogan in Brooklyn will clarify whether settlement immunity can shield ongoing architectural decisions. A ruling against Visa and Mastercard would open the door to rolling damages for each year of alleged overcharging—fundamentally altering the risk calculus for network fee structures.

Watch for defensive network rule changes. Visa and Mastercard may preemptively adjust interchange fee schedules or modify network routing rules to demonstrate good faith. Any such changes will ripple through clearing systems, fee calculation engines, and merchant reconciliation workflows. Builders should track updates to network operating rules and interchange rate tables.

Build flexible fee calculation and routing logic. Payment systems should decouple fee calculation from hardcoded rate tables. Implement configuration-driven interchange engines that can accept new fee models without code changes. Similarly, routing logic should support dynamic selection of lower-cost rails if network rules change.

Design settlement systems for retroactive adjustments. If the lawsuit succeeds, settlement systems may need to handle large-scale recalculations of historical fees. Architect for idempotent reprocessing, versioned settlement runs, and audit trails that can trace fee changes back to specific legal or regulatory events.

Engage with merchant coalitions. The plaintiffs represent a broader merchant movement. Understanding their economic arguments—particularly around interchange pass-through and network routing restrictions—will help architects anticipate where the next pressure points will emerge.

My Take

This lawsuit is not merely a legal skirmish over fees—it is a stress test on the architectural assumption that settlement immunity can indefinitely shield a structurally contested economic model. As a financial systems architect, I see this as a forcing function for designing payment systems that are legally resilient, not just technically robust.

The 2019 settlement was a band-aid on a structural imbalance. It allowed Visa and Mastercard to pay ~$6 billion in damages while preserving the interchange architecture that generated those damages in the first place. The new suit exposes that the underlying architecture of interchange—the formulaic determination of fees, the batch clearing process that calculates net positions, and the network routing rules that prevent merchants from choosing lower-cost rails—remains fundamentally contested. Settlement immunity bought time, not architectural legitimacy.

For architects, the implication is clear: the most defensible payment architecture is one where economic incentives are aligned with technical design, not shielded by legal settlements. If the court removes immunity, networks may face rolling damages for each year of alleged overcharging. That would force a redesign of fee calculation engines, reconciliation workflows, and routing logic to support transparent, auditable fee models.

I believe the future of payment architecture will move toward more modular, transparent fee structures that can withstand legal and regulatory scrutiny. Think of interchange as a configurable policy layer, not a fixed protocol constant. Systems designed with explicit fee schedule versioning, audit trails for rate changes, and dynamic routing to lower-cost rails will be better positioned to adapt—whether the legal outcome favors the networks or the merchants.

My position: the most resilient payment architecture is one where every economic rule is explicit, auditable, and contestable—because in the long run, legal architecture catches up to technical architecture.

Further Reading

For readers who want to deepen their understanding of the architectural and economic forces at play in this lawsuit, the following resources are recommended:

  1. Primary Source: The Payments Dive article “Visa, Mastercard face new suit over card fees” provides the factual basis for this analysis and is essential for understanding the legal timeline and merchant arguments.

  2. Merchant Economics Data: The Federal Reserve’s 2023 Interchange Fee Study offers empirical data on merchant costs, fee structures, and the distribution of interchange burdens across transaction types.

  3. Foundational Architecture Text: Bruce J. Summers’ The Payment System: Design, Management, and Supervision remains a definitive reference on settlement mechanics, clearing workflows, and the institutional design of payment networks.

  4. Regulatory Context: The CFPB’s report on Junk Fees in Consumer Financial Products frames the broader regulatory momentum against opaque fee structures that this lawsuit exemplifies.

  5. Architecture Primer: Arief W’s Payment Architecture Starter Notes (available on fintech.ariefw.com) covers authorization, clearing, settlement, tokenization, and reconciliation—the technical systems directly implicated by changes to interchange and routing rules.

Resources

News Source

Knowledge Base References

  1. Payment Architecture Starter Notes (private)
  2. Payment Architecture Starter Notes (private)

Manual Verification Checklist

  • Verify publication date and source credibility.
  • Check whether the announcement has a primary source.
  • Confirm company names, product names, and regulatory terms.
  • Add public technical references where possible.
  • Avoid citing private documents directly unless citation is allowed.