Mobile Wallet Competition Is Moving Beyond the Tap

Apple Pay, Google Wallet and Samsung Wallet may look increasingly similar from a consumer’s perspective. Add a card, authenticate, hold a phone near an NFC terminal and complete the transaction. For banks, payment companies and fintechs, however, the important differences increasingly sit below that interface.

A recent PaySpace Magazine comparison highlights how the three major mobile-wallet ecosystems have converged around NFC payments while continuing to diverge in areas such as peer-to-peer transfers, device integration and geographic availability. The more significant development for the payments industry is what this convergence reveals: competition is moving from the physical act of tapping a phone toward control over payment credentials, issuer access, wallet distribution and the surrounding regulatory framework.

NFC is becoming the baseline, not the differentiator

The basic contactless-payment experience is now broadly familiar. Google Wallet requires an NFC-enabled device, a supported payment method and appropriate device security before tap-to-pay can be enabled. Apple Pay similarly uses NFC for in-store payments, with authentication and payment credentials handled through Apple's device-security architecture.

Samsung historically had an additional differentiator through Magnetic Secure Transmission on supported devices, allowing payments at some terminals without NFC. Newer Galaxy devices increasingly rely on NFC, making terminal compatibility less distinctive than it was during the earlier phase of mobile-wallet competition. The result is that the front-end transaction is becoming relatively standardised. What is not standardised is everything required to make that transaction possible.

Issuer participation remains critical

A wallet does not automatically make every bank card usable. Google explicitly notes that banks decide whether their cards can be used with Google Wallet. Apple likewise relies on card issuers and payment networks during card provisioning. That makes issuer integration an important part of wallet distribution. Banks must decide which card portfolios to enable, manage provisioning and authentication, support tokenised credentials and deal with fraud, disputes and customer servicing around wallet transactions.

Apple's security documentation illustrates the model clearly. Rather than exposing the user's full card number during an Apple Pay transaction, a device-specific Device Account Number and a transaction security code are used to process payments. For financial institutions, the wallet may therefore be the consumer-facing layer, but the issuer and payment network remain deeply embedded in the transaction architecture.

Wallets are also expanding beyond card payments

Samsung provides a useful example of how that architecture is evolving. Samsung actually combined Samsung Pay and Samsung Pass into Samsung Wallet in June 2022, bringing payments together with digital IDs, keys, boarding passes and other credentials. The company then expanded the payments proposition again in 2025 with Tap to Transfer in the United States. The service enables users to send funds using debit-card credentials in Samsung Wallet, including certain transfers to recipients using other wallet platforms.

Google has taken a different path. It discontinued the standalone Google Pay app in the United States on June 4, 2024, including its P2P functionality, while retaining Google Wallet for card-based payments and digital credentials. Google Pay continued operating separately in markets including India and Singapore. The lesson is that "mobile wallet" no longer describes one uniform product category. In one market it may primarily be a tokenised card container. In another, it may also include P2P transfers, identity credentials, transit products or other services.

Regulation can change the competitive architecture

Europe adds another layer. In July 2024, the European Commission made Apple's commitments concerning iPhone NFC access legally binding. Under those commitments, qualifying third-party mobile-wallet developers established in the EEA can access NFC functionality using Host Card Emulation without being required to use Apple Pay or Apple Wallet. Users can also set eligible alternative applications as their default in-store payment app.

That is more than a product feature change. It affects who can potentially own the payment interface on a device. For banks and fintechs considering their own wallet propositions, similar changes can alter build-versus-partner decisions. But access to a device capability does not by itself settle the regulatory question.

The applicable perimeter depends on what the provider actually does: whether it merely supplies technology, initiates payments, issues payment instruments, holds customer funds or performs other regulated activities. Those distinctions vary by jurisdiction and business model and should be analysed before market entry.

The strategic question has changed

The consumer still sees a wallet icon and a tap.

The payments industry sees a much larger stack: device access, tokenisation, card-network connectivity, issuer approval, authentication, fraud controls, settlement relationships, local regulation and increasingly additional payment services layered around the transaction. That means comparing Apple Pay, Google Wallet and Samsung Wallet only by consumer features misses much of the competitive picture.

For banks and payment companies, the more useful question is becoming: which part of the wallet stack do we need to control, and which parts are better accessed through partners? As mobile wallets converge at the checkout, those infrastructure and regulatory choices are likely to matter more than another incremental change to the tap-to-pay experience.