PayPal launches Commerce, a toolkit for integrating buy buttons into apps, in closed beta
Context & Ripple Effects
This closed beta is PayPal formalizing a push that had been building for a year: One Touch checkout had already been extended into native mobile apps and Bigcommerce without requiring PayPal's own app, proving demand for payments that live inside someone else's interface. Commerce packages that capability as a developer toolkit — buy buttons any app can embed.
It also lands in a crowded lane. WePay had integrated an Instant Buy API months earlier as Google looked to expand Wallet use, so PayPal is racing rivals to become the default embedded-checkout layer rather than a button on merchant websites.
First-order effects
- App developers in the beta get a supported path to add one-tap purchasing inside their apps, extending the One Touch model beyond the e-commerce platforms it already served.
- WePay and other embedded-payments API providers gain a direct competitor with PayPal's brand recognition and merchant base behind an equivalent developer offering.
Second-order effects
- Platform owners become the prize: the same playbook later carried PayPal into Google's ecosystem via the Google Pay integration, after an earlier Android Pay partnership, as wallets sought checkout reach and PayPal sought distribution.
- Social and marketplace apps get a turnkey checkout option, which is how PayPal's commerce stack ended up powering Instagram Checkout and Facebook Marketplace before its general rollout to all merchants.
Third-order effects
- If the pattern holds, payment providers compete less on consumer wallets and more on who owns the embedded-checkout layer inside third-party apps — turning buy buttons into a distribution battleground between PayPal, WePay, and the wallet platforms themselves.
The trend: Payments are shifting from destination wallets to embedded checkout infrastructure, with API toolkits like PayPal Commerce deciding which provider sits inside everyone else's apps.