Windows 10 phones get NFC support as Microsoft rolls out update to Wallet, available to Windows Insiders now, will be generally available late summer
Microsoft is starting its rollout of tap-to-pay to certain U.S.-based Windows Insiders; general availability in the U.S. is ‘later this Summer.’
Context & Ripple Effects
Tap-to-pay reaches Windows phones more than a year after Windows 10's phone launch slipped past summer 2015, and it debuts the way Microsoft has staged the mobile OS throughout — first to Insiders on select hardware, echoing the Lumia-only preview from early 2015.
The timing is deliberate: fingerprint support lands on Windows 10 Mobile the same summer, supplying the biometric half of a contactless payment flow. And the wallet itself proves durable — two years later the same codebase resurfaces as Microsoft Pay inside Outlook, wired into Stripe, Braintree, Sage, and Wave.
First-order effects
- U.S. Windows Insiders on supported phones can make NFC tap-to-pay purchases today, serving as the test population before general availability 'later this Summer'.
- Microsoft gets a working payments surface on Windows 10 Mobile without waiting for the full consumer rollout of the OS.
Second-order effects
- The fingerprint rollout arriving the same summer completes the authentication side of the transaction, so the two updates function as a single tap-and-verify feature set for Insider testers.
- By 2018 the Wallet rail extends past phones into Outlook checkout with Stripe, Braintree, Sage, and Wave integrations — the payment infrastructure outliving the handset effort that seeded it.
Third-order effects
- With the phone launch already delayed once, the pattern points toward Microsoft treating the wallet less as a point-of-sale play and more as a cross-device checkout layer spanning PC, web, and inbox.
- If that holds, the durable asset is the payment rail and its merchant integrations rather than any single device category — the wallet functioning as a permission layer across form factors.
The trend: Mobile wallets are evolving from handset-bound tap-to-pay features into cross-platform payment layers whose rails persist even when the originating phone platform struggles.