Microsoft Pay, first debuted in 2016 as Microsoft Wallet, will roll out to Outlook users over coming months, integrating Stripe, Braintree, Sage, Wave, and more
Context & Ripple Effects
Microsoft Pay is the second act for Microsoft Wallet, which launched on Windows phones in 2016 around NFC tap-to-pay — a bet tied to hardware that never reached mainstream scale. Rather than abandon the asset, Microsoft is repositioning it as a service layer inside Outlook, plugging in third-party rails (Stripe, Braintree) and accounting tools (Sage, Wave) instead of running its own consumer wallet.
The move extends a playbook Microsoft has run in Outlook for years: add-ins from Uber, PayPal, Evernote, and Boomerang arrived in 2015, followed by app support on Outlook for iOS and LinkedIn contact enrichment in the inbox. Payments are the next capability bolted onto that surface — and the approach later resurfaces at larger scale when Microsoft brings payments into Teams with PayPal, Stripe, and GoDaddy for SMBs.
First-order effects
- Outlook users — particularly small businesses already invoicing through Sage or Wave — gain the ability to request and settle payments without leaving email, with Stripe and Braintree processing behind the scenes.
- Stripe and Braintree win distribution inside one of the largest business inboxes, while Microsoft converts a stranded mobile-wallet asset into a platform fee opportunity.
Second-order effects
- PayPal, which entered Outlook as an add-in back in 2015, now sits alongside rival processors inside Microsoft's client — pushing processor competition into the inbox itself rather than at merchant checkout.
- Accounting-software vendors like Sage and Wave get a native hook into the invoice-to-payment flow, tightening their lock-in with the small businesses that use both their books and Outlook.
Third-order effects
- If the pattern holds through the later Teams payments launch, Microsoft's productivity suite consolidates into a commerce channel where the software vendor — not the processor — controls where transactions originate, shifting bargaining power toward whoever owns the workflow.
The trend: Productivity suites are evolving from communication tools into transaction surfaces, with Microsoft embedding third-party payment rails directly into the workflows where invoices already live.