Apple Pay and Google Pay for your business: what it actually costs
By Yan Payments
Does accepting Apple Pay or Google Pay cost extra?
No. Turning on Apple Pay or Google Pay doesn’t cost you anything beyond what you already pay to accept cards. The wallet is just a different way for a customer to present a card that’s already on file with your processor. You’re charged the same interchange and processing rate you’d pay if that same card was tapped, dipped, or swiped directly. There’s no digital wallet surcharge sitting on top, and if a salesperson ever tells you there is, that’s a sign to get a second quote.
Where does the “wallets cost extra” idea come from?
Apple does charge a fee, just not to you. It charges the card’s issuing bank a small cut, reportedly around 0.15% per transaction in the US, for the privilege of putting that card inside Apple Wallet. That fee gets negotiated between Apple and the banks and comes out of the issuer’s side of the interchange split. It never touches your merchant statement. Google doesn’t charge banks the same way Apple does, but the result for you as a merchant is identical either way: the wallet layer is free to accept.
What you do pay is whatever your processor already charges for a tapped, contactless, card-present transaction. That’s actually the useful part of this story, because wallet transactions usually land in a cheaper bucket than you might expect.
Why can tapping a phone cost less than swiping a card?
Visa, Mastercard, Amex, and Discover all publish interchange rate tables with different pricing tiers depending on how a transaction happens. A chip-and-PIN or tap transaction where the card is physically present and cryptographically authenticated usually qualifies for a better, cheaper interchange tier than a manually keyed or swiped-and-signed transaction, because the networks see it as lower fraud risk.
Apple Pay and Google Pay transactions check every box the networks like: the card number itself is never transmitted (the wallet uses a tokenized, device-specific number instead), the transaction is cryptographically signed, and it’s authenticated by the phone’s biometric or passcode lock. From a risk standpoint, it looks a lot like a chip transaction, sometimes better. In practice, a customer tapping their phone is often no more expensive to accept than a chip tap, and can come in cheaper than a card that gets manually keyed in over the phone or swiped on an old-style terminal.
The exact tier a transaction qualifies for still depends on your processor’s pricing model (flat-rate, interchange-plus, tiered) and how your statement categorizes it. If you’re on a flat-rate plan like many small Clover setups, you won’t see tier-by-tier differences at all, you’ll just pay one blended rate regardless of how the card was presented. If you’re on interchange-plus pricing, it’s worth asking your processor to show you, line by line, what wallet transactions are qualifying as versus swiped or keyed ones.
Is fraud exposure lower with digital wallets too?
Yes. Because the wallet never shares your customer’s actual card number with your terminal, a data breach on your end can’t expose a usable card number, only a token tied to that one device. And because the transaction is authenticated by the phone itself, you’re generally in a stronger position if a chargeback dispute comes up, the same way a chip transaction protects you better than a swiped one.
Should you turn on Apple Pay and Google Pay?
If you’re already taking tap-to-pay cards on a Clover Flex, Mini, or Station, Apple Pay and Google Pay are almost always already enabled, since the wallets ride on the same NFC contactless antenna as a tapped card. There’s nothing extra to buy or activate in most cases. Check with Yan Payments if you’re not sure your current setup has it switched on. Given the growing share of customers who tap a phone instead of pulling out a wallet, especially anyone under 40, there’s no real downside to having it on.
The one thing to watch is daily transaction limits some processors set on contactless payments generally, which can occasionally require a PIN entry on a large purchase. That’s a network-level fraud control, not something specific to Apple Pay or Google Pay, and it rarely comes up for typical restaurant or retail ticket sizes.
The bottom line
Apple Pay and Google Pay don’t add a fee. They ride on your existing processing rate, and because they’re more secure than a swipe or a keyed card, they often qualify for the same or better pricing. If you’re deciding whether to turn tap-to-pay on for your business, cost isn’t the reason to hesitate. Compatibility with your current hardware is the only real question, and if you’re running Clover gear from the last several years, you likely already have it.
Sources
← Back to all posts