Google adds the ability to send and request money in Gmail via Google Wallet on Android in US
Context & Ripple Effects
This is the third channel Google has wired for peer-to-peer payments in under two years. It started with sending money to any phone number over SMS in late 2015, then removed the biggest friction point in August 2016 by letting Wallet balances transfer automatically to bank accounts instead of requiring a manual cash-out.
Embedding send-and-request directly into Gmail on Android turns the inbox itself into a payment surface — no separate app visit needed — and the related coverage shows where this leads: by May 2018 the same capability ships in Gmail's iOS app under the Google Pay brand, signaling the Wallet-era features were folded into a unified payments identity.
First-order effects
- US Android users can settle debts and request payment inside an email thread, giving Google Wallet a distribution channel with Gmail's reach rather than relying on standalone app installs.
Second-order effects
- The automatic bank-transfer feature becomes load-bearing: because received money moves straight to users' bank accounts, a Gmail payment request is viable even for recipients who would never keep a Wallet balance — widening the pool of usable payers beyond active Wallet users.
Third-order effects
- If the pattern holds — SMS in 2015, Gmail Android in 2017, Gmail iOS via Google Pay in 2018 — Google's payments strategy is surface-first: distribute transactions across every communication product it owns, then consolidate the underlying brand, which is exactly the Wallet-to-Pay collapse the later coverage shows.
The trend: Google is turning its communication surfaces — SMS first, then Gmail — into native payment rails, with the wallet itself receding into an invisible layer behind a unified Pay brand.