Apple Pay and Google Pay: the hidden economics of the wallet button

Apple Pay and Google Pay are no longer the checkout extras they were a decade ago. What started as a way to tap a phone at a coffee shop has become a structural layer of the payment stack: the button that sits at the top of most e-commerce checkouts, the default tap on most POS terminals, and the experience against which raw card forms are now measured. In 2026 the question is not whether a merchant should accept them, but whether they are treating them as a payment method or as a conversion lever.

The user experience is the obvious place to start, and it is the reason the wallets keep winning. A customer with Apple Pay or Google Pay set up can complete a purchase in roughly half the taps of a traditional card form. There is no card number to type, no expiry date to remember, no CVC to flip the phone around for, and no 3D Secure pop-up that feels like it came from another decade. On a mobile browser, where the majority of e-commerce traffic now lives, that friction gap is decisive. Studies across the industry consistently show that Apple Pay checkouts convert 10 to 20 percent higher than raw card forms on iOS, and Google Pay delivers a similar lift on Android. The wallet does not change the product or the price. It simply removes the moments at which a customer can change their mind.

For users, the advantages run deeper than convenience. Security is the less visible but more important benefit. Apple Pay and Google Pay do not hand the merchant a real card number. They use a tokenisation layer that creates a device-specific account number and a dynamic security code for every transaction. Even if a merchant's database is breached, the stolen credential is useless elsewhere. The real card number never leaves the secure element on the phone or the watch. On Apple devices the authentication is biometric — Face ID, Touch ID, or a passcode — and on Android it is the screen lock plus Google Pay's own token vault. The result is that the payment is both faster and safer than typing a card into a web form.

This security model also shifts the fraud liability in useful ways. Because the wallet payment is authenticated with a strong biometric or device-bound factor, the rates of fraudulent acceptance are materially lower than card-not-present transactions. For merchants, that means fewer chargebacks, fewer manual reviews, and fewer interventions from the fraud stack. For users, it means fewer false declines and fewer instances of a legitimate purchase being blocked because the issuer's risk engine did not like the look of a new device.

The merchant case is where the story gets more interesting than the marketing. A merchant enabling Apple Pay or Google Pay does not just add another button. It gains access to the payment credentials the user already trusts. The wallet is pre-loaded with cards, addresses, and delivery details that the user has verified with their device and, in many cases, their bank. That changes the economics of onboarding. The merchant no longer needs to collect, store, and protect a primary account number. The payment provider no longer needs to run the same level of card-not-present fraud checks. The conversion funnel shortens and the risk profile improves at the same time.

The reach is also significant. Apple Pay is available in more than 80 markets, Google Pay in more than 90. Both are accepted by the vast majority of contactless terminals in the markets where they operate, because they ride on the same EMV contactless infrastructure as physical cards. For a merchant, that means a single wallet integration unlocks in-store, in-app, and online payments in one credential. For a global merchant the operational simplicity is real: one tokenised rail, one reconciliation stream, one set of dispute workflows, rather than a patchwork of local card schemes and banking rails.

Where the wallets sit against cards is the part that depends on geography. In the United States, mobile wallets are now the dominant in-store contactless experience. Apple Pay alone accounts for more than half of US in-store mobile wallet usage, and when Google Pay and the other wallets are added, the category is well ahead of the still-common plastic card tap. Online, the picture is more fragmented: cards still own the bulk of transaction value, but Apple Pay is responsible for a meaningful share of consumer e-commerce payments, and wallets as a category are growing faster than cards. The trend is not that cards are disappearing; it is that the wallet is becoming the first choice, and the card is becoming the fallback.

In Europe, the landscape is more nuanced because of the continent's dense network of local payment methods. iDEAL, Bancontact, BLIK, Swish, and the open-banking wallets built on SEPA Instant all compete seriously with cards. Apple Pay and Google Pay do not have the same market dominance as in the US, but they have become the standard universal wallet at the top of the checkout. For cross-border merchants, they solve a problem that local schemes cannot: a traveller from France can pay in Germany with the same wallet they use at home, and a UK shopper can buy from a Spanish merchant without exposing card details to a website they have never visited. That makes them complementary to local APMs rather than competing with them.

Wallets are not replacing cards; they are replacing the card form as the default first interaction.

The market share data tells the same story. Across the EU, alternative payment methods — including wallets, pay-by-bank, and local schemes — now account for more than half of e-commerce value. In France, Apple Pay and Google Pay together make up 17 percent of online payments. In the US, Apple Pay holds more than half of in-store mobile wallet usage and is accepted by 85 percent of retailers. The broader shift is that the wallet layer is becoming the aggregation point: the user thinks in terms of "pay with Apple Pay" or "pay with Google Pay" rather than "pay with this Visa or that Mastercard." The card brand moves to the background, and the wallet brand moves to the foreground.

For merchants, the practical implications are threefold. First, wallet acceptance should be treated as table stakes at the top of the checkout, not buried below the card form. Second, recurring and subscription flows should support wallet-based credentials where possible, because tokenised wallets update automatically when the underlying card is replaced, reducing involuntary churn. Third, in-app and mobile-web experiences should be optimised for wallet-first checkout, because that is where the conversion lift is largest.

For users, the future is likely to be more wallet-centric, not less. As more payment cards, loyalty cards, transit tickets, and identity credentials move into the phone's secure wallet, the device becomes the natural hub for the transaction. The choice between Apple Pay and Google Pay will remain largely a function of the device ecosystem, but the underlying behaviour — authenticate with biometrics, pay with a token, expose nothing to the merchant — is converging. The wallet is the interface; the card is the rail behind it.

That is why the comparison with cards is increasingly the wrong framing. Cards are still the money movement layer. They are still the instrument that moves funds, the network that routes transactions, and the brand that offers rewards and chargeback rights. But the wallet is the interface layer. It determines how easy the payment feels, how secure the credential is, and which payment method the user actually chooses. Merchants that optimize only for cards are optimizing the infrastructure, not the experience. And in 2026, the experience is what wins the checkout.