Finance & Unit Economics

Stripe and Square: the Take-Rate Model

Stripe · Fintech / payments · 2011 Beginner

Stripe charges roughly 2.9 percent plus 30 cents per transaction, a cut small enough to feel like a rounding error. Run it across billions of transactions a year and it becomes one of the most enviable business models in software. When Stripe launched in 2011, accepting payments online meant wrestling legacy bank systems; it collapsed that into a few lines of code. Square did the same for in-person payments with a reader that plugged into a phone, putting credit-card acceptance in the hands of food trucks and farmers markets.

For founders and operators, the lesson is in the math of taking a percentage of a flow rather than a flat fee: revenue grows with your customers' success without you touching the product or the price. But the model only works under specific conditions about the flow itself. This case sharpens the decision of whether your business should charge for value delivered instead of a fixed price, and where in your industry a large, sticky, growing flow sits with no efficient intermediary taking a cut. The conditions that make or break it are what the app has you name.

Topics
  • Stripe
  • Square
  • take rate
  • payments
  • fintech
  • unit economics
  • revenue model
  • scalable margins
  • platform business
  • transaction fees

Apply this case

Don't just read it. Apply it.

CaseBook turns this story into a move you use this week, with an AI coach that pressure-tests your thinking against your own company.

Coming soon to the App Store

7-day free trial, then $5.99/mo or $49.99/yr. Cancel anytime.