Source: Google to announce new payments API, Android Pay, at I/O in May
Google will launch Android Pay at I/O in May — Source tells Ars that the company will revitalize its payments platform with a new API. — A source close to the matter told Ars on Wednesday that Google …
Context & Ripple Effects
Two years into Google Wallet's slow start, a source tells Ars the company is rebuilding its payments stack around Android itself: Android Pay, to be unveiled at I/O in May, will handle both in-store NFC and in-app checkout, while Wallet gets relaunched separately as a peer-to-peer app per the related I/O announcement coverage. The structural difference is the API — TechCrunch's follow-up framed it as giving developers the reins, meaning any app can embed payments rather than routing through Google's own storefront.
That developer-first framing is what separates this from a Wallet rebrand, and the arc held: within three months Google shipped it publicly with over 1,000 apps and 700K US stores supported, and by 2016 had opened integration to all developers.
First-order effects
- Android developers gain a native payments API at launch, letting them add checkout without building card flows themselves, while Google gets a payments surface on every NFC-capable Android phone instead of a single Wallet app users had to adopt.
Second-order effects
- Apple Pay, which the same coverage shows adding rewards programs, now competes against a payments layer pre-installed on the larger global phone base — pushing loyalty features to the center of both platforms' pitches.
- Banks become distribution partners rather than bystanders: Android Pay's later reach into Bank of America ATMs (2016) shows issuers integrating tokenized Android payments directly into their own hardware.
Third-order effects
- If the pattern holds, payments stop being a product and become an OS capability — Google iterated the same API into its 2017 Payment Request-era checkout and loyalty offerings (targeted Android Pay offers via Assistant), suggesting the long game is a platform take-rate on transactions flowing through Android apps.
- Wallet-scale consumer fintech then consolidates around whoever controls the OS-level credential store, leaving standalone wallet apps to compete only where the platform player doesn't.
The trend: Mobile OS makers are absorbing payments into the platform layer itself — shipped as APIs to developers rather than standalone wallets — with Google's Android Pay the Android-side answer to Apple Pay's head start.