Android Pay Google Wallet with NFC
By FF Newsroom · 10 March 2015
Google is overhauling its mobile payments strategy with the introduction of Android Pay, a new API-driven platform designed to challenge Apple Pay’s growing dominance. By shifting from a proprietary app to an open developer framework, Google aims to leverage Android’s massive global footprint to achieve the mainstream adoption that eluded its original wallet.
What was announced
Google is planning to re-launch its mobile payment initiative under the name Android Pay, moving away from the proprietary model of the original Google Wallet. This new platform is structured as a payment API rather than a standalone offering, allowing device manufacturers and third-party developers to integrate payment capabilities directly into their own applications and hardware. This shift is intended to solve previous adoption hurdles, such as the reluctance of telecom providers to pre-install specific wallet software on new handsets.
The strategy follows Google’s acquisition of intellectual property from Softcard, a move made to strengthen its position after Apple Pay’s market entry. A key technical component of the new strategy involves Host Card Emulation (HCE). Since the Android Kit Kat release, the operating system has provided built-in support for HCE, and there is a strong possibility this will be integrated into the Android Pay API to support devices that lack a built-in NFC radio or Secure Element.
Geographically, the move targets Android’s 80% worldwide market share, with a particular focus on the US market where digital natives and younger users form a significant portion of the base. The open API approach also presents an opportunity for financial institutions to integrate payments into their existing mobile banking apps, a long-standing goal for the sector that could lead to more seamless reward program integrations.
The companies involved
Google, the developer of the Android operating system, was a pioneer in the mobile wallet space, being the first to utilize NFC technology in the US. Despite this early start, the original Google Wallet struggled due to a lack of strategic partnerships and resistance from telecommunications providers. To rectify this, Google brokered a deal with Softcard, a now-defunct mobile payments joint venture previously backed by major US carriers, to acquire key IP and clear the path for a wider rollout through revenue-sharing schemes with telcos.
Android currently maintains a dominant position in the global smartphone market, holding approximately 80% of the worldwide share. This ecosystem is characterized by its open-source nature and a highly fragmented hardware landscape, ranging from high-end flagship devices to budget handsets in developing nations like India and Africa. While the platform boasts a massive user base, it faces a significant gap in average revenue per user (ARPU) compared to iOS. Analysis suggests Android users generate only a quarter of the revenue of their Apple counterparts, which remains a central factor in how Google positions its financial services against established competitors.
What this means
The pivot to an open API model is a calculated gamble that volume can overcome Apple’s head start in user experience. By allowing banks to "own" the payment experience within their own apps, Google is addressing a major pain point for financial institutions that felt sidelined by proprietary wallets. However, the fragmented nature of the Android ecosystem remains a significant threat. If Google cannot ensure a consistent experience across thousands of different device types, it risks another "false start." The real test will be whether this open approach can drive higher transaction volumes among a user base that historically spends less than iOS users, particularly in markets where direct carrier billing is already the standard.