Google's New In-App Payments Product Set For Launch In May 2011
Google was originally set to debut in-app payments support for Android in the fourth quarter of 2010, and recently said that the launch would be delayed until the end of this quarter. Be that as it may, the company is set …
Context & Ripple Effects
Google has been promising native in-app payments on Android since late last year, and after a slip from Q4 2010 to the end of Q1, the company now has a May 2011 target. It is a return to familiar territory: back in November 2006 Google rolled out features for Checkout while waiving merchant fees to buy adoption on the web, and in-app billing extends that payments push from the browser into the app layer of its mobile OS.
The delay matters because Android developers have been building subscription and virtual-goods models against third-party billing workarounds in the meantime — every quarter without an official product is a quarter of friction Google does not control.
First-order effects
- Android developers finally get a first-party in-app purchase mechanism, replacing ad-hoc billing integrations once the May product ships.
- Google gains a direct transaction touchpoint inside apps, extending its Checkout-era payments infrastructure onto the device.
Second-order effects
- Rival smartphone platforms face pressure to match first-party in-app billing rather than leave developers to third-party payment SDKs, since the official option becomes table stakes for monetizing apps.
- Payment providers whose Android business rests on custom in-app integrations risk displacement wherever Google's built-in flow becomes the default.
Third-order effects
- If the pattern holds, OS-level payments become a structural feature of mobile platforms — commerce bundled with distribution — repeating the subsidize-to-adopt play Google ran with Checkout's fee waivers in 2006, this time at the operating system layer.
The trend: Mobile platforms are absorbing payments into the OS itself, turning app-store owners into default transaction intermediaries for their developer ecosystems.