Stripe is a financial technology company founded by brothers Patrick and John Collison around 2010, originally under the name /dev/payments before launching publicly as Stripe in 2011. Its premise was that accepting payments on the internet should be a programming problem solved by developers, not a months-long bank and gateway integration handled by a business team. Stripe became one of the defining examples of a company whose product is fundamentally an API.
The heart of Stripe is its REST API. Stripe’s own reference describes it plainly: “The Stripe API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.” This consistency, combined with test-mode keys and copy-paste code samples, let a developer move from sign-up to a working charge in minutes. The early marketing distilled this into the idea of accepting a payment in only seven lines of code.
Stripe treated developer experience as the product surface. Its documentation, language-specific libraries, and sandbox environment were engineered so that the path of least resistance was also the correct integration. Stripe’s engineering writing on API design emphasizes that “abstracting away the complexity of payments has driven the evolution of our APIs,” and that an integration must be “extremely predictable and consistent” rather than littered with special cases in the docs.
Over time the company expanded far beyond a single charge endpoint into subscriptions, invoicing, in-person payments, marketplaces, and money-movement products, each exposed as additional resources on the same API. This breadth made Stripe a platform that other businesses build on rather than a single feature, reinforcing the model in which a company exposes its core capability as a programmable service.
Stripe is frequently cited alongside Twilio as a company that proved the commercial power of the API economy: rather than selling software to be installed, it sold a clean, reliable interface to a hard problem, and let an entire ecosystem of other software call it. The Collisons’ bet that developers, not procurement, would choose payment infrastructure became a template that later API-first companies followed across many industries.