Android Pay's debut means Google Wallet will live on as a P2P payments app
If you're not reaching, engaging, and monetizing customers on mobile, you're likely losing them to someone else. Register now for the 8th annual MobileBeat, July 13-14, where the best and brightest will be exploring …
Context & Ripple Effects
Google has spent months rebuilding its payments strategy after Wallet failed to gain traction: a February report had it paying wireless carriers and sharing mobile ad revenue to buy distribution, and by March Android Pay had emerged as a developer-facing API rather than a consumer app. The I/O announcement two days ago laid out the split — Android Pay for in-store and in-app purchases, Wallet relaunched around person-to-person transfers — just as Apple moved to add rewards to Apple Pay.
Today's news confirms that structure is real: one brand for tapping phones at registers and inside apps, another for sending money between people. The split matters because it separates the two businesses Wallet had conflated — merchant acceptance, where Google competes head-on with Apple Pay and the card networks, and P2P, where the fight is over engagement frequency.
First-order effects
- Android Pay goes live for payments across more than 1000 apps and roughly 700K US stores, making it the default tap-to-pay layer on Android devices.
- Google Wallet users lose the tap-to-pay function they knew and are redirected to a narrower P2P product, betting retention on how often people send money to each other.
Second-order effects
- Apple's parallel move to bolt rewards onto Apple Pay turns merchant incentives into the competitive battleground — both platforms must now pay (in rewards or, per Google's reported carrier deals, revenue shares) for placement they once expected to win on OS default.
- Developers gain an Android Pay API to embed checkout directly into their own apps, shifting integration cost away from merchants and toward Google's developer relations.
Third-order effects
- Splitting payments into separate brands proved unstable: within three years Google folded Android Pay and Wallet together under a single Google Pay brand, suggesting the P2P-versus-retail division created more user confusion than clarity.
- If platform owners keep treating wallets as distribution assets rather than standalone products, payment branding will follow OS cycles — consolidated, renamed, and repositioned at each gatekeeper's convenience.
The trend: Mobile payments are consolidating into OS-level wallet layers controlled by platform gatekeepers, with standalone apps surviving only where they serve a distinct job like P2P.