Judge certifies every US card issuer that paid Apple Pay fees as one antitrust class

When someone taps an iPhone with a credit card to pay $100, the card's issuer owes Apple 15 cents under the fee schedule described in the lawsuit ^[3][13]. On a debit card the issuer owes half a cent, whatever the purchase size ^[3].

The cardholder picks the phone and taps. According to the complaint, the issuer has no say: it pays because Apple Pay is the only tap-to-pay option on an iPhone ^[7]. The plaintiffs argue Apple could not keep charging "substantial fees" if it had to let other wallets onto its devices ^[8].

Certification changes who can make that argument. The fee defines the class. Any US entity that issued an Apple Pay-enabled card and paid Apple on those transactions is a member ^[2]. The lawsuit names credit unions and other small financial institutions among the issuers paying what it calls supracompetitive fees ^[10]. Hagens Berman, the firm representing the plaintiffs, said Judge Jeffrey White "denied Apple's motion to exclude expert testimony attorneys say establishes common proof that Apple maintains monopoly power in a relevant antitrust aftermarket for tap-and-pay iOS mobile wallets as well as a broader market for all mobile wallets" ^[5].

Certification lets issuers pursue the claim as a group ^[11]. It does not decide the claim. The "up to $1 billion" a year is the plaintiffs' figure ^[4], and until the court rules, issuers still owe 15 cents on every $100 credit tap ^[13].

Issuers can already build on another route. Apple has let developers offer NFC contactless payments in their own apps since iOS 18.1, including in the US ^[12]. In principle, an issuer can ship its own iPhone tap-to-pay wallet today. The reports do not say what Apple charges for that access or whether any card issuer has shipped one.

An issuer's position turns on two things. The first is portfolio mix. The credit fee grows with ticket size and overtakes the flat debit fee on any purchase above about $3.33. At $100 it is 30 times the debit charge ^[14][15]. The second is whether the team can ship and support an in-app NFC wallet.

That gives four positions. A credit-heavy issuer that can build has the most at stake in the damages claim, and it is the only case where the fee alone can justify a wallet project. For a credit-heavy issuer that cannot build, the class claim is the main option, and its record of fees paid is what makes it a class member ^[2]. A debit-heavy issuer that can build pays half a cent a tap, so a wallet needs a reason other than the fee ^[3]. For a debit-heavy issuer that cannot build, little changes on Monday.

In my view, only the first group should cost out a wallet project now. The rest should keep an accurate fee ledger and let the class pursue the claim. The price of waiting is the full fee for as long as the case runs, and it has run since 2022 ^[4].