Apple Pay and Google Pay are usually still card-network sales. You pay interchange to the issuing bank, assessments to the brand, and processor markup. Neither wallet typically adds a merchant-side fee on U.S. in-person NFC, or on in-app and web checkout that uses the wallet as a card credential. The wallet changes how the card is presented (a payment token, tapped or passed in software). It does not replace the three fee layers. Typical total processing fees are often described as 1.5 percent to 3.5 percent of the transaction plus a per-item fee (U.S. Chamber of Commerce, 4 Jun 2026). Treat that as a typical range, not a quote. The wallet brand is not a fourth wholesale line.
Set by the card networks, paid to the issuing bank. An NFC tap is usually card-present. In-app and web are card-not-present.
Network dues. Pass-through. Same family as a plastic-card sale on the same brand.
The only layer anyone competes on. May include a fee to turn the wallet button on. Apple and Google typically add $0 on the merchant bill.
A wallet is a tokenized card, not a new rail
When a customer adds a Visa or Mastercard to Apple Pay or Google Pay, the network's token service issues a payment token (often called a device PAN) in place of the plastic account number. The merchant and the terminal see the token and a cryptogram, not the printed card number. Apple's consumer pages put it this way: a device-specific number and unique transaction code, so the actual card number is not shared with the merchant or stored on Apple servers (Apple Pay, accessed August 2026).
That token is still a card credential on Visa, Mastercard, Discover, or American Express. Settlement still runs through your acquirer. The PCI Security Standards Council treats an EMVCo Payment Token, used as specified and sitting outside the token service provider's environment, as not Account Data (PCI SSC FAQ 1326, May 2015). Systems that still store, process, or transmit a real PAN stay in scope. A wallet tap does not erase PCI DSS.
Four channels that people collapse into "mobile"
In-person NFC tap. Phone or watch to an NFC reader, or to Tap to Pay on iPhone. Apple Support (16 Dec 2024) is explicit: for in-store purchases the merchant's devices must have NFC contactless enabled, and the merchant must accept the card's payment network. This is contactless card-present. Same family as a chip dip or a plastic tap. See card-present vs keyed vs e-commerce.
In-app. The customer hits the Apple Pay or Google Pay button inside your app. Same wallet, different capture. This is card-not-present / e-commerce, even if they are standing at your counter.
Web. Safari, another browser, or a scanned code that completes on the phone. Still remote. Still card-not-present.
App Store digital goods. Buying an app, a game, or a subscription inside Apple's store is not your merchant account taking Apple Pay. It is Apple's store checkout, billed under Apple's store rules. Do not put that commission on your processing model.
Google Pay for Developers (accessed August 2026) states the merchant rule in one line: Google doesn't charge any additional fees to accept Google Pay. Standard processing fees from your payment provider still apply. Apple's public FAQ (accessed August 2026) tells cardholders Apple does not charge fees when they pay with Apple Pay in stores, online, or in apps, and tells businesses that already take cards to contact their payment provider to turn it on.
Who pays Apple, and who pays you
Do not mix three bills.
The merchant bill is interchange, assessments, and markup, plus any gateway fee to enable the button. That is what hits your statement.
The issuer bill is separate. The U.S. Department of Justice, in its 21 Mar 2024 complaint, alleges Apple "extracts a 0.15 percent commission from banks on credit card transactions through its digital wallet, while none of its smartphone competitors with digital wallets charge any fee." That 15 basis points, if collected, comes from the issuing bank, not from your settlement. It is not a line you can negotiate off a merchant statement.
The cardholder bill is the purchase. Apple's FAQ says Apple does not add a consumer fee to pay with Apple Pay.
U.S. banks collected nearly $66 billion in interchange in 2025 (Federal Reserve Bank of St. Louis, 9 Apr 2026). Wallet volume sits inside that pile. It does not sit beside it.
Capture is what moves interchange
You cannot talk a network off its table. You can stop putting a present card into a remote bucket. Visa USA Interchange Reimbursement Fees, effective 18 Apr 2026, price consumer credit All Other Products like this (wholesale to the issuer, not your merchant discount):
| Channel | Visa program | Interchange on a $100 sale |
|---|---|---|
| NFC tap at a terminal | Card-present Product 2 | 1.51% + $0.10 = $1.61 |
| In-app or web, no token incentive | Card-not-present Product 1 | 1.89% + $0.10 = $1.99 |
| In-app or web, EMV token (Type 1) | Product 1 minus 0.05% | 1.84% + $0.10 = $1.94 |
Illustrative. Confirm the category names on your statement. Traditional Rewards and Signature Preferred sit higher on the same tables. Fail the program rules and both tables list Non-Qualified Consumer Credit at 3.15% + $0.10.
Visa's card-not-present page also publishes incentives: EMV token transactions qualify for Type 1 (-0.05%), Digital Commerce Authentication Program (DCAP) for Type 2 (-0.10%), and DCAP plus EMV token for Type 3 (-0.15%), with listed exceptions (Visa USA Interchange Reimbursement Fees, 18 Apr 2026). A wallet in-app sale often carries an EMV token. That can shave a few basis points off the remote row. It does not reclassify the sale as card-present.
Regulated debit is the other exception. Under the Federal Reserve's Regulation II, debit interchange received by issuers with $10 billion or more in assets is capped at 21 cents plus 5 basis points, plus up to 1 cent if fraud-prevention standards are met. Small issuers are exempt. Visa's regulated column is 0.05% + $0.21 (plus $0.01 when the issuer certifies) on retail, key entry, and e-commerce alike. A wallet does not break the cap. Markup and gateway fees still can.
Hardware and the gateway button
In person, the requirement is NFC, not a wallet contract with Apple or Google. If the terminal already takes contactless plastic, it already takes wallet taps on that network. Tap to Pay on iPhone is the other path: a supported payments app, no extra terminal. Apple's merchant FAQ (accessed August 2026) says to ask your payment provider; Apple's Tap to Pay pages describe accepting contactless cards, Apple Pay, and other wallets on the same iPhone.
Online and in-app, someone has to register a merchant identifier, host the button, and decrypt the payload. That is gateway and processor work. Some providers include it. Some add a monthly or per-auth line to turn the button on. Ask for that line in writing. Do not assume it is $0 because Apple and Google are $0.
A new wallet button is not a new merchant ID. It is another capture path on the MID you already have.
How to read it on the statement
Wallet volume rarely prints as "Apple Pay" or "Google Pay" as a surcharge. On an interchange-plus statement it prints as retail contactless, e-commerce, token, or the program name Visa or Mastercard assigned. On a tiered or flat statement those buckets fold into one rate, which is how a remote wallet mix hides inside a "qualified" teaser.
Add every processing line for the period, including PCI, batch, gateway, and monthly extras. Divide by gross card volume for the same period. That effective rate is what the mix cost, wallet taps included. If in-app share is rising and effective rate is rising with it, you are watching capture, not a secret Apple tax.
What to change, and what not to
You cannot negotiate Apple's issuer fee. You cannot negotiate Visa's published row. You can:
- Keep in-room cards on the terminal. Do not key a present card "because they have Apple Pay on the phone." Ask them to tap.
- Treat in-app and web as remote. Price and operate them that way. Token and authentication programs are the levers on that row, not a promise the wallet is "like cash."
- Ask the gateway what the button costs. Monthly, per-auth, or bundled. Get it on the agreement.
- Recompute after the mix shifts. If effective rate did not move, the volume was already cheap, or markup ate the gap.
Interchange-plus makes the categories visible. Tiered and flat hide them. None of those models erases the network row. If you would rather not hunt the rows by hand, upload last month's statement. As-billed first, including whether the sale was a tap or a button.
FAQ
Does Apple Pay cost merchants extra in the United States? Not as a wallet brand fee. An in-store Apple Pay tap is a contactless card-network sale. You pay interchange, assessments, and processor markup, the same three layers as plastic. Apple's public FAQ (accessed August 2026) says Apple does not charge fees when you pay with Apple Pay in stores, online, or in apps. Confirm any gateway enablement fee on your contract.
Is Google Pay cheaper for merchants than Apple Pay? On the merchant bill, both are usually the same card economics. Google states it does not charge additional fees to accept Google Pay; standard processing fees from your payment provider still apply (Google Pay for Developers, accessed August 2026). Capture method and card product move the dollars, not the logo on the phone.
Is a phone-wallet tap at the register card-present? Yes, when the phone or watch taps an NFC terminal in person. That is contactless card-present. Paying with the same wallet inside an app or a browser is card-not-present, even if the customer is standing in your store.
Why does in-app Apple Pay or Google Pay cost more than an in-store tap? Capture, not the wallet brand. Visa's U.S. consumer-credit table prices card-present Product 2 at 1.51% + $0.10 and card-not-present Product 1 at 1.89% + $0.10 on All Other Products, effective April 18, 2026. In-app and web sit in the remote family. Token incentives can shave a few basis points. They do not turn a browser checkout into a tap.
Do I need a special terminal to accept Apple Pay or Google Pay? In store you need NFC contactless enabled, or Tap to Pay on iPhone through a supported payments app. Apple's merchant FAQ (accessed August 2026) says if you already accept credit and debit, contact your payment provider. Online and in-app, the gateway or checkout has to offer the wallet button. That is software, not a new MID.
Is App Store checkout the same as Apple Pay on my website? No. Apple Pay on your site or in your own app is still a card-network sale through your processor. Buying digital goods inside Apple's App Store is a different product, billed under Apple's store rules, not your merchant statement. Do not mix the two when you model fees.
Sources
- Apple, Apple Pay (consumer FAQ: fees, how a business accepts Apple Pay), accessed August 2026
- Apple Support, "Learn where to use Apple Pay," 16 Dec 2024
- Apple Developer, Tap to Pay on iPhone: How to accept payments
- Google Pay for Developers, "No additional fees," accessed August 2026
- U.S. Department of Justice, United States et al. v. Apple Inc., Case 2:24-cv-04055, complaint filed 21 Mar 2024
- Visa USA Interchange Reimbursement Fees, rates effective 18 Apr 2026
- Visa, Credit Card Processing Fees and Interchange Rates (merchant download page)
- Federal Reserve, Regulation II (Debit Card Interchange Fees and Routing)
- Federal Reserve Bank of St. Louis, "Credit and Debit Card Fees Collected by U.S. Banks Rose in 2025," 9 Apr 2026
- U.S. Chamber of Commerce, "How to Calculate Credit Card Processing Fees," 4 Jun 2026
- PCI SSC FAQ 1326, "How does PCI DSS apply to EMVCo Payment Tokens?", May 2015
Questions about how this applies to your business?
Talk it through