Stripe
Infra / DevOps · Usage-based
Overview
A set of tools that lets businesses take payments online and handle the money side of running a business. It was started in 2010 by brothers Patrick and John Collison. At its core it moves card and bank payments from a customer to a business, then handles payouts, refunds, and reporting. Around that core it adds pieces for recurring billing, invoices, sales tax, fraud checks, in person card readers, and marketplace payouts. Developers connect to it with code, and there is also a dashboard for people who do not write code. It is used by small shops and by large public companies.
What people use it for
Common users are software companies, online stores, and marketplaces. They use Stripe to take one time card payments at a website or app checkout. They run subscriptions and recurring billing, including trials, discounts, and prorated plan changes. They send invoices to other businesses and collect payment by card or bank transfer. They calculate and collect sales tax, VAT, and GST across many countries with Stripe Tax. They pay out sellers or service providers on a marketplace using Stripe Connect. They accept payments in person with Stripe Terminal card readers. They screen payments for fraud with Stripe Radar before a charge goes through. They also pull payment data into reports and dashboards, sometimes querying it with SQL through Stripe Sigma.
Key capabilities
Stripe processes payments in 135 or more currencies and works with businesses across many countries, with local bank connections in 46 markets. It supports payment methods beyond cards, including wallets such as Apple Pay and Google Pay and regional options. Stripe Billing handles subscriptions, metered usage, invoices, and revenue reports. Stripe Tax calculates and helps file indirect tax across many countries. Stripe Radar screens payments in real time using machine learning and adds custom rules on higher plans. Stripe Connect runs payouts for platforms and marketplaces and onboards connected accounts. Stripe Terminal provides pre certified card readers for in person payments. Sigma lets teams query their Stripe data with SQL. Standard card pricing is a percent plus a flat fee per successful charge, with an added fee on international cards. Disputes carry a fee, and payouts to external accounts on some products carry a small percentage fee.
Limitations
Standard fees sit on the higher side and are hard to negotiate until volume is large. Pricing is mostly per transaction, so cost rises directly with sales. Chargeback disputes carry a fee even when the business wins, though newer dispute options change how that works. Payout timing is set by Stripe and can feel slow and rigid for new accounts. Account reviews and holds happen with limited explanation, and support for smaller accounts is mostly docs and email. Some products, such as Financial Connections, only work with United States bank accounts. Building a full checkout still needs developer time.
Insight
Stripe is usually the fastest way for a team to start charging customers. The documentation is clear, the libraries are well kept, and most common billing cases are already handled. The trade is cost and control. Standard fees are not the cheapest, and they do not move much until a business is processing large volume. Payout schedules, dispute handling, and account reviews follow Stripe's rules, not the customer's, and getting a person on the phone is hard below enterprise size. Some teams outgrow the standard pricing and move part of their volume to a cheaper processor while keeping Stripe for the parts that are painful to rebuild. For most companies that calculation comes later. Early on, the setup speed and the quality of the tools are worth more than a lower fee. Best when time to launch matters more than the last fraction of a percent.
Pricing
Usage-based
Website
Last checked 2026-08-30