Accepting Apple Pay and Google Pay: what merchants actually need to know
Apple Pay and Google Pay are tokenized versions of the cards your customers already carry: the phone stores a network token, authenticates the payer biometrically and pays over NFC in-store or through a wallet button online. For merchants they cost nothing beyond normal card fees, typically skip the $250 contactless PIN ceiling because the device authenticated the buyer, and carry lower fraud rates than plain card entry, which is why wallet-enabled checkouts convert better.
Scope: For merchants deciding whether wallet acceptance is worth configuring, and what changes at the counter and the checkout when it is.
What actually happens when a phone taps your terminal
When a customer adds a card to Apple Pay or Google Pay, the issuer replaces it on the device with a network token: a stand-in number bound to that phone. At the counter, the customer authenticates with a glance or a fingerprint, the phone emits the token plus a one-time cryptogram over NFC, and your terminal treats it like any contactless card. The real card number never touches the device's radio, your terminal, or your systems.
For your costs, nothing changes: the transaction routes through the same networks at the same interchange as the underlying card, and neither Apple nor Google charges the merchant. (Apple takes a small fee from the issuing bank, which is the bank's problem, not yours.) A wallet tap is, from your statement's point of view, simply a card-present contactless payment, and often a slightly safer one.
The two behaviours merchants notice at the counter
First, big taps go through. Plain contactless cards worldwide generally stop at a $250 tap ceiling and demand insertion with PIN above it. A wallet payment carries its own cardholder verification, the biometric, so issuers typically approve wallet taps well above the plastic ceiling. Staff who have been telling customers 'over the limit, please insert' can watch a phone tap sail through on the same amount.
Second, fraud exposure drops. A stolen card can be tapped by anyone until cancelled; a stolen phone still demands a face or fingerprint before it pays. Combined with tokenization, wallet transactions consistently show lower fraud rates than their plain-card equivalents, which quietly benefits your dispute statistics.
Online: where wallets stop being a convenience and start being conversion
In-store, wallets are a nicer tap. Online, they are a different checkout. A wallet button replaces the entire card form, number, expiry, CVV, billing address, with one sheet the customer confirms biometrically; shipping and contact details flow from the wallet itself. On mobile screens, where typing sixteen digits kills carts, this is the difference between a checkout attempted and a checkout abandoned.
The security economics online are equally friendly: the wallet transaction arrives tokenized and device-authenticated, satisfying strong-authentication logic and shrinking the fraud surface that card-not-present payments normally carry. Merchants get CNP reach with something much closer to card-present risk.
Setup is configuration rather than contract: with RapidCents, NFC terminals accept wallets out of the box, and hosted checkout, payment pages and Rapid.js expose Apple Pay and Google Pay buttons with domain verification handled during onboarding. The work is measured in minutes, and the wallet share of your volume will tell you within a month whether your customers were waiting for it.
Frequently asked questions
Do merchants pay extra fees for Apple Pay or Google Pay?
No. Wallet transactions cost the merchant the same as the underlying card would: same networks, same interchange, no wallet surcharge. Apple collects a small fee from card issuers, not from merchants; Google charges neither.
Does Apple Pay have the $250 tap limit?
Generally no. The contactless ceiling exists because a plain tap involves no cardholder verification; wallet payments carry biometric verification on the device, so issuers typically approve wallet taps above the plastic limit. Individual issuers set their own policies, but large wallet taps routinely succeed where plain-card taps would demand a PIN.
Is Apple Pay safer for the merchant than a physical card?
Modestly, yes. The transaction is tokenized, so no reusable card number passes through your systems, and the payer was biometrically authenticated, so stolen-card taps largely disappear. Lower fraud on the transaction means fewer fraud disputes landing on you.
What do I need to accept wallets in my store?
An NFC-capable terminal, which every modern certified terminal is. If your device accepts tap, it accepts Apple Pay and Google Pay today; no separate registration or agreement exists for in-store wallet acceptance.
How do I add Apple Pay to my website checkout?
Through your payment provider's checkout tooling: domain verification plus enabling the wallet buttons. With RapidCents hosted checkout and Rapid.js, the buttons are a configuration switch, and they appear automatically only on devices that support them.
