The archive · Business Models · Product decision · 2011
Stripe turns online payments into an API — no merchant account, just 2.9% + 30¢ per charge
Stripe's 2011 launch made payments developer-first: no merchant account or gateway, no setup or monthly fees — just 2.9% plus 30 cents per successful charge.
Stripe
What it had to solve
In 2011, accepting credit cards online meant getting a merchant account from a bank, adding a payment gateway, and paying monthly and transaction fees — weeks of friction that filtered out small sites and startups. Brothers Patrick and John Collison believed the problem was rooted in code, not finance.
How it works
In 2011, accepting credit cards online was a small-business filter. You needed a merchant account from a bank that had to approve you, a payment gateway, monthly fees, and contracts — weeks or months before a site could charge anything. Patrick and John Collison, who had sold their first startup while still teenagers, believed the problem was code, not finance.
Stripe launched publicly in September 2011 as a payments platform for developers. Sign-up took minutes: APIs for Ruby, PHP, and Python, no merchant account or gateway to arrange, cards stored in Stripe's secure environment, and payouts straight to a bank account. It charged one flat rate — 2.9% plus $0.30 per successful charge — with no setup, monthly, or card-storage fees.
The design made checkout a feature the developer controlled: Stripe's API let sites build and brand their own payment forms and keep customers on their own page instead of redirecting them. The company's stated belief — enabling transactions on the web is a problem rooted in code, not finance — turned a payments company into a developer tool.
Why it lands
- Stripe reframed payments as a code problem, not a finance problem — putting the product in developers' hands instead of banks'.
- One flat per-transaction fee removed negotiations, tiers, and hidden costs, so price never blocked adoption.
- No merchant account or gateway deleted the hardest, slowest step from the customer's checklist.
- Letting developers own the branded checkout page solved a real drop-off problem merchants cared about.
- The Collison brothers' track record and backing from PayPal founders gave a tiny startup instant credibility with developers.
What it did
The model removed the two things that had made payments painful — merchant accounts and price uncertainty — and made checkout a feature developers controlled. Within a year Stripe had a growing base of U.S. developers, expanded to Canada, and its flat per-charge pricing became the template for developer-first fintech.
What you can take
Attack the unsexy bottleneck: the barrier wasn't price, it was setup pain — so Stripe simplified the product and made the fee so transparent it stopped being a reason to hesitate.
Since then
Stripe kept the flat-fee model as it grew: it added subscriptions, marketplace payouts, and international expansion, and its checkout products became the default payment rails for startups. The 2.9% plus 30 cents formula became an industry baseline that later payments startups copied, and a few lines of code became the standard promise of payment APIs.
Sources
- Sequoia-Backed Stripe Wants To Disrupt The Online Payments Space
- Payment Processor Stripe Goes Loonie
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card