Stripe made online payments easier for developers, then expanded through the businesses and platforms they built.
High setup and upkeep costsBarriers to participation
A developer could publish software online yet spend days arranging card acceptance and connecting it to a checkout. Merchant applications and payment integration could delay charging for a product; some developers left their applications free. Hosted payment pages offered another route, but sent buyers through a separate checkout experience. ST1
Step 1 of 3 · 2010 to 2013
Patrick Collison recalled building web applications that never charged users because setting up payments kept slipping down the work list. Stripe gave developers a short path from signup to accepting cards on their own sites. Paul Graham, a YC investor, described the founders taking a willing user’s laptop and installing the product immediately. ST1 ST3
The product and the sales method addressed the same obstacle: unfinished integration. A developer could see a working payment flow before committing a separate business team to a bank and gateway project. Hands-on installation helped the founders turn interest into use; the API made that work repeatable.
The founder and investor accounts establish actions and early user response, not the share of subsequent growth attributable to installation.
Rivals Hosted PayPal checkout and merchant-account-plus-gateway setups were available. Stripe’s distinction was developer control and getting a working integration into the application.
Step 2 of 3 · 2012 to 2026
Connect lets a software platform onboard sellers, route payments and pay them out through Stripe. The platform can earn from those payments while retaining its own customer relationship. Stripe reported serving more than five million businesses directly or through platforms in its 2025 update. ST4 ST6
One platform integration can distribute payment services to many merchants. Ben Thompson’s thin-platform analysis helps explain this division of work: Stripe supplies a financial foundation while other software companies build the specialized products around it. Those partners have a commercial reason to distribute the service. ST7
Platform participation is documented; the public figure combines direct and platform users and cannot measure Connect’s incremental acquisition effect.
Rivals Direct merchant acquisition requires separate integrations and selling. Connect joins the platform’s existing merchant workflow; competing infrastructure providers can pursue the same route.
Step 3 of 3 · 2023 to 2026
Intercom needed billing that could handle changing AI product prices and outcome-based charges. Its old implementation consumed engineering time and made changes difficult. Stripe worked with Intercom on a phased migration covering new products, existing customers and older billing arrangements. ST5
Taking over billing gave Stripe a larger job than authorizing a card payment. It connected pricing rules, subscriptions and accounting work. That helped Intercom launch its commercial changes, and it creates a qualified switching-cost mechanism: replacing the provider again means remapping those rules and migrating live customers. The cost depends on how much of the workflow each customer adopts.
Supplier-published customer testimony is selected. Migration effort supports the mechanism but does not quantify Stripe’s retention advantage.
Rivals Intercom’s existing billing implementation is the observed alternative. The migration demonstrates that customers can leave a provider when the replacement benefit justifies the work.
Oldest first.