Apple Pay's Fee Fight Is Really About Who Controls the Wallet

Apple Pay is a perfect payments product in one very specific sense: the customer sees almost none of the machinery underneath it.

You double-click, authenticate, tap the terminal, and leave.

Behind that clean experience sits a much messier set of relationships among Apple, card issuers, payment networks, merchants, wallet providers, and the technology that determines who can actually reach the customer at the point of sale.

That hidden layer is now at the center of a significant antitrust case.

On September 23, 2026, U.S. District Judge Jeffrey S. White certified a class in Affinity Credit Union et al. v. Apple Inc. covering U.S. entities that issued Apple Pay-enabled payment cards and paid Apple fees on Apple Pay transactions. The lawsuit, originally filed in 2022, alleges that Apple used its control over tap-to-pay functionality on iPhones to restrict competing mobile wallets while charging issuers fees for Apple Pay transactions.

That ruling matters, but let's be precise about what it means.

The court did not rule that Apple violated antitrust law. It did not decide that Apple Pay's fees were unlawful. Class certification means qualifying issuers can pursue common claims together as the litigation continues.

For payments companies, though, the case is worth watching for a reason that goes beyond Apple.

It's about what happens when control over a payment interface turns into commercial leverage.

The fee is only half the story

According to the plaintiffs' allegations, Apple charges U.S. issuers 0.15% on credit card transactions made through Apple Pay and $0.005 on debit card transactions. The plaintiffs argue that those fees could be sustained because competing tap-to-pay wallets historically couldn't access the iPhone's NFC functionality on equivalent terms.

The plaintiffs' theory is not simply, "Apple charged us a fee and we don't like it."

The theory is that the fee and the competitive environment around that fee are connected.

That distinction matters.

Payments companies charge fees all the time. Processors charge fees. Networks charge fees. Gateways charge fees. Platforms charge fees. Banks charge fees. Software companies increasingly charge fees around embedded payments products.

A fee by itself isn't an antitrust case.

The harder question is whether a company controls something competitors need in order to reach the market, and whether that control changes what the company can charge or what alternatives customers realistically have.

That's where the Apple Pay case becomes much more relevant to the rest of payments.

When technical architecture becomes commercial architecture

For years, the iPhone wasn't just another distribution channel for mobile wallets. Apple controlled the device, the operating system, the NFC functionality used for contactless payments, and Apple Pay itself.

The plaintiffs allege that competing wallets couldn't use the iPhone's NFC capabilities to offer their own tap-to-pay experience while Apple Pay could. They contrast that structure with Android, where multiple mobile wallets have been able to compete for contactless transactions.

In 2024, the European Commission made Apple's commitments to open NFC access to rival wallet providers legally binding after raising competition concerns about Apple's control over tap-and-go payments on iPhone. Separately, Apple introduced its NFC & Secure Element Platform beginning with iOS 18.1, allowing authorized developers in eligible markets, including the United States, to build secure contactless experiences outside Apple Pay and Apple Wallet.

Today, Apple's developer documentation says eligible users can select a qualifying third-party app as their default contactless application. Developers still have to meet Apple's eligibility, security, privacy, regulatory, technical, and contractual requirements, and Apple's documentation says the required agreement includes commercial terms and applicable fees.

In other words, the architecture has changed.

But that doesn't automatically answer the legal question about the period being challenged in the lawsuit. And it doesn't make the underlying payments lesson disappear.

Technical access rules can be economic rules.

If your API determines who can participate, your API policy can affect competition. If your operating system determines which wallet can launch at the terminal, a product decision can become a market-access decision. If access requires a contract, the contract can become part of the economics of reaching the customer.

Payments teams tend to separate these conversations. Product owns the integration. Legal owns the contract. Finance owns the pricing. Compliance owns the requirements.

The Apple Pay dispute is a good example of why those boxes don't stay separate for long.

The customer experience can create negotiating leverage

There's another uncomfortable reality underneath the case: consumers like good payment experiences.

Once customers expect to pay with a particular wallet, card issuers have a business reason to support it. Telling an iPhone customer that their card simply won't work in Apple Pay isn't a great retention strategy.

The plaintiffs' complaint argues that this customer demand limited issuers' practical ability to avoid Apple Pay fees by simply refusing to participate.

Whether that argument ultimately succeeds is for the court to decide. But the commercial dynamic should look familiar to anyone who works in embedded payments.

Distribution creates leverage.

A software platform with thousands of merchants has leverage with a payments provider because it controls distribution. A marketplace can have leverage because it controls seller access. A processor can have leverage because migration is expensive. A device ecosystem can have leverage because customers already live inside it.

None of those things are inherently improper.

But every payments partnership should ask the same basic questions before the leverage becomes obvious:

• What does each party actually control?
• Which parts of the relationship can be replaced?
• What happens to pricing if switching becomes difficult?
• Are technical access rights guaranteed contractually, or can they change?
• Who owns the customer relationship?
• What fees scale automatically with transaction volume?
• What happens if the underlying platform changes its rules?

Those aren't just procurement questions. They're payments strategy questions.

Small fees become big economics at scale

One reason this case resonates in payments is that the challenged pricing looks tiny when you view it one transaction at a time.

Fifteen basis points doesn't sound dramatic in a conference room.

At payment scale, it can become very real money.

The plaintiffs allege Apple collects as much as $1 billion annually from the challenged issuer fees. That figure remains an allegation, not a judicial finding, but it illustrates why seemingly small layers in the payments stack deserve attention.

Payments economics accumulate.

Interchange. Network assessments. Processor markup. Gateway fees. Tokenization costs. Fraud tools. Chargeback expenses. Platform fees. Wallet economics. Revenue share.

An ISV can negotiate aggressively over a few basis points with its processor while barely noticing another fee sitting elsewhere in the stack.

The lesson isn't to treat every fee as suspicious. The lesson is to understand what you're paying for, why you're paying it, whether there are alternatives, and what happens when volume increases by 10x.

Opening the interface doesn't end the conversation

Apple's current NFC & Secure Element Platform makes this case more interesting because the market structure is no longer exactly what it was when the lawsuit began.

Eligible third-party apps can now offer NFC payment experiences on supported iPhones. Users can choose an eligible default contactless app. Apple says the platform is separate from Apple Pay and Apple Wallet.

That is meaningful.

It also raises the next set of questions payments companies should expect whenever a previously closed interface opens.

How difficult is qualification? What technical work is required? What security and regulatory obligations apply? What commercial terms govern access? Can a competing provider create an experience customers will actually adopt? Is access technically available but economically unattractive?

Competition isn't just whether an API exists.

It's whether a credible alternative can use it.

That distinction is going to matter well beyond mobile wallets as commerce becomes increasingly controlled by operating systems, app stores, AI agents, super apps, embedded payment platforms, and other software layers sitting between the customer and the underlying financial rails.

The payments lesson is bigger than Apple Pay

The easy version of this story is that banks are suing Apple over Apple Pay fees.

The more useful version is about dependency.

Payments businesses are increasingly built on infrastructure controlled by somebody else. That might be a card network, processor, sponsor bank, cloud provider, mobile operating system, app marketplace, or AI platform.

Every dependency comes with technical rules. Most come with commercial rules. Some eventually become strategic leverage.

The Apple Pay litigation is still ongoing, and Apple has not been found liable for the antitrust claims at issue. But the case is already a useful reminder that payment economics can't be evaluated separately from platform control.

When you're negotiating a payments relationship, don't just ask what the fee is.

Ask what gives the other party the ability to charge it.

That's usually where the more interesting risk is hiding.

Want to get featured on the CentsChat podcast? Complete our survey.