Android Pay Is Real, And Will Give Developers The Reins As An API
Darrell Etherington / TechCrunch :
Context & Ripple Effects
This report lands between the leak and the launch: days earlier, a source told Ars that Google would unveil a new payments API called Android Pay at I/O in May, and this piece confirms the plan is real — with the twist that developers get direct access via an API rather than a closed wallet product. When Android Pay formally arrived months later, it spanned over a thousand apps and 700K US stores, and Google's older Wallet service was repositioned as a P2P payments app, leaving the merchant and developer layer to the new platform.
First-order effects
- App developers gain a payments primitive they can embed directly, rather than routing checkout through Google Wallet's consumer-facing flow — shifting integration work from Google to third-party engineering teams.
Second-order effects
- Google can seed adoption with incentives once the rails exist: by December, Android Pay was live in mobile apps with discounts at partners like OpenTable, Lyft, and DoorDash to drive first use.
Third-order effects
- Opening integration to all developers, as later happened alongside Bank of America ATM support, points toward Android Pay becoming default payment infrastructure across Android rather than one wallet among many.
The trend: Mobile payments are consolidating into platform-owned APIs, where the OS vendor sets the rails and developers build the checkout experiences on top.