What actually competes with a Visa debit transaction?
That sounds like a simple question.
It is not.
Mastercard debit seems obvious. PIN debit networks belong in the conversation. Then someone mentions ACH. Someone else says pay-by-bank. Real-time payments show up. Wallets get thrown in. Stablecoins eventually arrive because it is 2026 and apparently no payments conversation is allowed to end before somebody says stablecoin.
Suddenly we are not arguing about debit anymore.
We are arguing about what a payment actually is.
That question sits underneath the U.S. Department of Justice's antitrust case against Visa. The DOJ alleges that Visa has unlawfully maintained monopoly power in debit network markets and used agreements, pricing, and other practices to protect that position from competing debit networks and alternative payment methods. Visa disputes the government's characterization of the market and its competitive position.
The legal case will be decided on legal facts and arguments far beyond the scope of a blog article.
But the underlying question is extremely relevant to ISVs and platforms:
When a customer needs to move money from a bank account to a merchant, what options actually compete for that transaction?
Because the answer changes how you think about routing, pricing, network power, product strategy, and the future of payment acceptance.
Antitrust cases spend a lot of time defining markets because market share only means something after everyone agrees on what market they are measuring.
If you define the market narrowly as debit network services, the competitive landscape looks one way. If you define it broadly as every mechanism capable of moving money from a consumer to a merchant, the landscape looks completely different.
Imagine a town with one pizza restaurant. If the market is pizza, that restaurant has 100% share. If the market is food, suddenly it competes with burgers, tacos, sushi, grocery stores, and the questionable sandwich sitting in the office refrigerator.
Payments has the same problem, only with more acronyms.
Visa debit competes directly with other debit network options. But does it also compete with ACH? Pay-by-bank? RTP? Cash? Credit cards? Digital wallets? Stablecoins?
Technically, many of those can accomplish the same high-level objective: move value from the buyer to the seller.
Commercially, however, they are not necessarily interchangeable.
That distinction matters.
Payments people love architecture diagrams where every rail sits neatly next to every other rail.
Card. ACH. RTP. FedNow. Pay-by-bank. Wallet. Stablecoin.
Look at all the choices.
The problem is that a merchant cannot necessarily swap one for another without changing the customer experience, economics, risk model, settlement model, dispute process, integration, reconciliation, or conversion rate.
A debit card works because the consumer already has one, merchants broadly accept it, the credential fits existing checkout experiences, authorization happens quickly, and decades of infrastructure sit behind the transaction.
ACH can move money from the same checking account, but the payment experience and risk characteristics are different.
Pay-by-bank can potentially bypass card rails, but customer adoption, bank connectivity, authentication, conversion, returns, disputes, and merchant integration all matter.
RTP and FedNow can move funds quickly, but acceptance at consumer checkout is not the same thing as having a real-time payment rail available.
Stablecoins can move value efficiently in certain environments, but asking whether they currently substitute for mainstream U.S. consumer debit acceptance is a very different question from asking whether stablecoins can move money.
Capability is not the same as substitutability.
ISVs understand something payment economists can occasionally underappreciate: the payment method is part of the product experience.
A merchant does not only care whether money eventually arrives. The merchant cares whether the customer recognizes the payment method, trusts it, completes the checkout, understands the authorization flow, receives a refund cleanly, can dispute a problem, and comes back next month.
Conversion matters.
That makes payment substitution harder than comparing transaction costs on a spreadsheet.
Suppose pay-by-bank costs less than debit. Great. If customers abandon checkout because they do not want to connect their bank account, the cheaper rail may be extraordinarily expensive.
Suppose another rail settles instantly. Great. If refunds become operationally painful, support costs increase, or reconciliation becomes worse, speed did not solve the whole problem.
Payments economics cannot be separated from payment behavior.
The cheapest transaction is not automatically the cheapest payment experience.
The Durbin Amendment and the Federal Reserve's debit routing rules made network choice and routing a strategic issue by requiring debit cards to support competing unaffiliated network options.
Merchants and their payment providers can potentially route eligible debit transactions across competing networks based on economics, performance, acceptance, fraud, and other considerations.
In theory, that creates competition.
In practice, routing is complicated.
The merchant may not control the decision directly. The processor may make routing decisions. The gateway may influence what data is available. The transaction type may limit options. Tokenization can affect routing. Card-not-present transactions create different considerations than card-present transactions. Network incentives can change the economics. Processor contracts can change the economics again.
This is why "least-cost routing" has always been an incomplete phrase.
Lowest network cost according to whom?
Before or after incentives?
Including processor markup?
Including authorization performance?
Including fraud?
Including operational complexity?
Routing is an economic decision hiding inside infrastructure.
The payments industry has spent years pitching alternatives to cards with some variation of the same promise:
Cards are expensive. Use this instead.
Sometimes that is compelling.
But card networks did not become enormous simply because merchants forgot to look for cheaper options.
They solved a collection of problems at the same time: acceptance, credentials, authorization, fraud controls, consumer familiarity, disputes, refunds, global interoperability, settlement, rules, and reliability.
Alternative rails do not have to copy cards exactly. In fact, copying every part of the card model would defeat some of the reason to build alternatives.
But they do need to solve enough of the merchant and consumer problem to become a genuine substitute.
A cheaper rail that customers do not use is not competitive pressure.
A faster rail that merchants cannot easily integrate is not competitive pressure.
A technically elegant rail with poor dispute handling may be perfect for one use case and terrible for another.
Competition happens at the use-case level.
This is where things get interesting for software platforms.
Historically, merchants often accepted whatever payment methods their processor made available.
Modern ISVs increasingly sit closer to the actual payment decision. They own checkout. They know the customer. They know the merchant. They know the transaction type. They may control orchestration across multiple processors or payment methods.
They can potentially decide whether a transaction should use debit, credit, ACH, pay-by-bank, a wallet, or another rail based on economics and customer preference.
That makes the ISV more than a software company with payments attached.
It can become the routing intelligence layer.
But only if it actually controls enough of the stack.
If every payment decision ultimately disappears into one processor integration, the platform may have less strategic control than the product roadmap suggests.
This is why processor portability, token ownership, routing data, network economics, and multi-processor architecture matter.
Payment choice only exists when you can actually exercise it.
You cannot optimize routing if you do not know what the routes cost.
That sounds painfully obvious.
Yet plenty of platforms cannot clearly explain the economics of individual payment methods.
They know their merchant price. They may know their processor rate. They may not understand interchange, network fees, routing costs, incentives, processor markup, authorization performance, fraud losses, and operational cost at enough detail to compare one route with another.
Then someone says, "Let's add pay-by-bank because it is cheaper."
Cheaper than what?
For which merchants? At what ticket size? With what conversion? With what return rate? With what support burden? With what reconciliation cost? With what incentive impact?
Alternative rails become strategically useful when platforms can measure them against the real economics of the incumbent payment method.
Otherwise, you are comparing marketing decks.
Competition does not necessarily mean Visa debit disappears.
The existence of credible alternatives can influence pricing, product investment, network rules, incentives, and merchant negotiations even when the incumbent rail remains dominant.
A merchant does not need to move every debit transaction to another rail. It needs enough realistic choice that the incumbent knows the merchant can move something.
The same is true for ISVs.
Processor diversification changes negotiations even if most volume stays with the primary processor. Alternative payment methods change negotiations even if cards remain the default. Routing control changes negotiations even if the cheapest network does not win every transaction.
Optionality has value.
Payments companies frequently underestimate that value because optionality does not show up neatly as a line item on the processor statement.
It shows up when you renegotiate.
Payments debates have a strange obsession with declaring winners.
Cards versus ACH. Cards versus pay-by-bank. Cards versus stablecoins. RTP versus cards. Wallets versus cards.
Usually the answer is less exciting.
Different rails are good at different things.
Debit may remain extremely strong at consumer checkout. ACH may remain excellent for recurring bank-account payments and B2B use cases. Real-time payments may become valuable where immediate settlement matters. Pay-by-bank may gain traction where merchants can create enough consumer value to change behavior. Stablecoins may become important for cross-border settlement, treasury, machine payments, and other use cases where traditional rails are inefficient.
The future is probably multi-rail.
Which means the strategic advantage may belong to whoever can choose intelligently among them.
What actually competes with a Visa debit transaction?
The legal system will wrestle with its own version of that question in the DOJ's case against Visa.
ISVs and platforms should ask a slightly different version:
What can realistically replace this transaction for this merchant, this customer, and this use case?
Not theoretically.
Actually.
If another rail is cheaper but destroys conversion, it is not a substitute. If another rail is faster but creates operational problems, it may not be a substitute. If another network is available but your processor controls routing and keeps the economics opaque, your theoretical choice may not be much of a choice.
Payment competition is not just about how many logos appear on a checkout page.
It is about whether merchants and platforms have meaningful control over how money moves.
Payments Therapist helps ISVs, platforms, PayFacs, and payment companies understand the economics, contracts, routing options, processor dependencies, and operational realities underneath those choices.
Because having multiple rails is nice.
Knowing when you can actually use them is strategy.