§ 01 · Why Stripe became the default

“Before Stripe, accepting cards online was genuinely terrible. The improvement was so large that nobody could quite believe it.”

Henrik, you spent eight years inside Stripe. For someone who wasn’t in the payments industry in 2010, can you explain why Stripe took over the way it did?

You had to be there to fully appreciate it. Before Stripe, if you wanted to accept credit cards on a website, the typical setup involved applying for a merchant account through your bank, integrating with a payment gateway like Authorize.net, signing a separate processor agreement, dealing with PCI compliance paperwork directly, and waiting six to twelve weeks for the whole thing to come online. The setup fees were often in the hundreds of dollars. The documentation was uniformly bad. The APIs — where APIs existed at all — were XML-based and felt like they had been designed in 1998. Which, in some cases, they had been.

And then?

And then Stripe shipped. You could go from zero to accepting your first credit card payment in about twenty minutes. Seven lines of code. No merchant account application. No paperwork. No setup fee. The pricing was flat and printed clearly on the homepage — 2.9 percent plus thirty cents per transaction, no monthly fee, no gateway fee, no statement fee. The documentation was actually readable. For developers and small business owners who had been wrestling with the old system, it felt like someone had finally noticed that accepting payments online in 2011 should not require a part-time consultant.

That was fifteen years ago. What is Stripe’s actual advantage for small businesses today?

The competition has caught up on the developer experience, broadly. Adyen is excellent. Square is genuinely good for in-person. PayPal’s API has improved dramatically over the last five years. So Stripe’s edge is no longer that it’s the only good option — it’s that Stripe is consistently the best default for a specific kind of business. That business is roughly: online-first, sells anywhere from $0 to $2 million per year in card volume, wants transparent pricing, doesn’t want to negotiate, and benefits from a deep ecosystem of integrations with the rest of the modern software stack. That description covers about 80 percent of small businesses operating online today. And for that 80 percent, Stripe is still the right answer.

§ 02 · What 2.9 percent + 30 cents actually buys you

“The headline rate is honest. The end-of-month statement is where people get surprised.”

Stripe’s standard pricing is famously 2.9 percent plus thirty cents per transaction. Is that actually what most small businesses end up paying?

For domestic, online, standard credit card transactions in their home country, yes. That headline rate is genuinely what you pay. It includes processing, gateway, PCI compliance, fraud screening through Radar, and most of the infrastructure that used to be billed separately. That part is straightforward, and Stripe deserves credit for not playing pricing games at the headline level the way some competitors do.

Where do small businesses get surprised, then?

Three places, consistently. The first is international cards. Any card issued outside the United States — or your home country if you’re outside the US — carries an additional 1.5 percent. If a meaningful share of your customers pay with international cards, the effective rate is closer to 4.4 percent than 2.9 percent. Most small businesses don’t realise this until they look at a statement and see the line item.

The second?

Currency conversion. If your business accepts payments in multiple currencies and converts to a single home currency for payout, Stripe adds 1 percent on top of the underlying exchange rate. The exchange rate itself isn’t terrible — it’s close to the interbank rate — but the 1 percent on top is invisible at the moment of payment. It shows up in the reconciliation, and many small businesses operating internationally don’t notice it for the first few months.

And the third?

Disputes and chargebacks. Stripe charges $15 per disputed transaction, regardless of whether you win the dispute or lose it. That fee is non-refundable. For most businesses this is barely a cost, but for businesses in categories with elevated dispute rates — digital subscriptions, online education, anything where customers can claim ”I didn’t authorise this” with some plausibility — the chargeback fees can become a meaningful line item. A business doing $50,000 a month in subscriptions with a 0.5 percent dispute rate is looking at $375 a month in dispute fees alone. That’s before the actual disputed transaction value is also reversed.

Anything else worth flagging?

Instant Payouts, if you use them. Stripe’s standard payout schedule is rolling — usually two days in the US. If you want money in your bank account today, Stripe offers Instant Payouts for a 1 percent fee. It’s a fair price for the service, but it’s another line that can creep into the effective rate if you turn it on as a default. The honest summary: the headline rate is honest for typical domestic transactions, and the additional fees are all legitimate and disclosed, but the combined effective rate for an internationally-operating subscription business is closer to 4 to 5 percent than 3 percent. Plan for the higher number.

§ 03 · The reserves question

“Stripe rarely places reserves on established small businesses. The exceptions are predictable.”

PayPal is famous for freezing accounts and holding funds. Does Stripe do the same?

Stripe is significantly more measured than PayPal, but it can and does place reserves on certain accounts. The triggers are predictable once you know what they are. The first is a rapid increase in processing volume that doesn’t match the business profile on file — if you onboarded as a small online store doing $5,000 a month and suddenly process $200,000 in a week, that gets flagged. The second is operating in a category Stripe considers higher risk, which includes adult content, digital goods, supplements, anything related to credit repair or debt consolidation, and certain e-commerce categories where chargeback rates are historically elevated.

And the third?

A sudden spike in dispute or chargeback rate. If your dispute rate crosses 0.75 percent of processed volume, Stripe’s systems flag the account automatically. If it crosses 1 percent, there’s typically a manual review. Beyond that, reserves or in extreme cases account closure become real possibilities. For most well-run small businesses, dispute rates sit between 0.05 and 0.3 percent and this is never an issue. But for businesses experiencing fraud, payment-processing abuse, or a category-specific dispute pattern, this is the thing to watch.

If Stripe does place a reserve, what does it look like in practice?

Two common forms. A rolling reserve holds back a percentage of every payout — typically 5 to 25 percent — for a defined period, usually 90 to 180 days. After the period, the reserved funds release. A minimum balance reserve requires you to maintain a specific dollar amount in your Stripe balance at all times. Stripe communicates the reserve terms in writing when they apply one, and there’s usually a path to having the reserve reduced or removed once the underlying concern resolves — better dispute rates over time, additional documentation about the business, sometimes just a few months of clean processing history. It’s less arbitrary than PayPal’s reputation suggests, but it’s also not negligible if you’re running a business with thin cash flow margins.

§ 04 · When Stripe isn’t the right answer

“The honest cases for Square, Adyen, or PayPal.”

You mentioned 80 percent of small businesses should use Stripe. Who’s in the other 20 percent?

Three categories. The first is in-person, brick-and-mortar businesses where the bulk of revenue comes from physical card payments rather than online. Stripe Terminal exists and works fine, but Square is genuinely better for this specific case. Square’s hardware is more polished, the in-person UX is more refined, the staff onboarding is simpler, and the per-transaction rate for in-person card-present payments is lower at 2.6 percent plus 10 cents versus Stripe’s 2.7 percent plus 5 cents. The difference is small but real, and for a coffee shop or hairdresser the ergonomics of Square’s ecosystem matter more than they would for an online business.

The second?

Businesses processing above approximately $2 million annually. At this scale, Adyen’s volume-based pricing becomes meaningfully cheaper than Stripe’s flat 2.9 percent, and the savings are large enough to justify the additional integration work. Adyen’s pricing isn’t published — you negotiate — but typical effective rates for businesses at this scale land between 1.8 and 2.3 percent depending on the mix of card types and regions. Over a year of $2 million in volume, that’s $12,000 to $22,000 in savings versus Stripe. At $5 million, it’s $30,000 to $55,000. The integration is harder, but the math works.

And the third?

Businesses whose customers strongly prefer PayPal at checkout. This is most common in certain demographics — older customers, certain international markets, particular product categories like collectibles and hobby goods — where PayPal’s brand recognition genuinely affects conversion rates. The right answer here is usually to offer both: Stripe as the primary processor for card transactions, with PayPal as a supplemental checkout option for customers who specifically want it. The dual-processor setup is more work to maintain, but if 20 to 30 percent of your customers convert better through PayPal, the work pays for itself.

§ 05 · The lock-in nobody discusses

“Stripe is genuinely good. It’s also genuinely hard to leave.”

You mentioned earlier that one of the underrated costs of Stripe is the cost of eventually leaving it. Walk me through that.

Stripe has, over the years, built one of the most extensive ecosystem moats in fintech. Once your business is on Stripe, you’re typically also using Stripe Billing for subscriptions, Stripe Tax for compliance, Stripe Connect if you have marketplace functionality, Stripe Capital if you’ve taken financing, Stripe Atlas if you incorporated through them, and dozens of integrations — your accounting system, your CRM, your subscription analytics, your customer portal, your tax filing tool — that all read data directly from Stripe’s API. The deeper that integration gets, the harder it becomes to move.

What does an actual migration off Stripe look like?

Painful, in proportion to how integrated you became. The customer data is portable — Stripe is genuinely good about helping with card data migration and they’ll provide tokenised card details to a competing processor in a PCI-compliant way. That part is fine. What’s painful is everything else. Re-implementing subscription logic in a different processor. Recreating tax compliance rules. Rebuilding webhook integrations across every adjacent tool. Reconnecting accounting and reporting. For a business with a deep Stripe footprint, a full migration is typically a six-figure project and three to six months of engineering work. That cost isn’t advertised when you sign up, and it should be.

Is this an argument against using Stripe?

No. It’s an argument for being aware. For 80 percent of small businesses, Stripe is the right answer and the integration depth is a feature, not a bug — the ecosystem is genuinely useful and switching costs only matter if you have a strong reason to switch. But for businesses thinking about Stripe as a temporary stop on the way to a more custom payments infrastructure, or for businesses likely to be acquired or to merge with a company on a different processor — it’s worth knowing the actual exit cost before optimising for the deepest possible Stripe integration. Use Stripe’s value-added services where they save you real time. Avoid them where they create lock-in for marginal benefit.

§ 06 · The verdict

“If you’re starting a small online business in 2026, start with Stripe. The question is only when, if ever, to leave.”

Bottom line for a small business owner deciding right now?

Use Stripe. For the typical online small business doing under $2 million a year, there is no realistic alternative that beats Stripe on the combination of pricing transparency, integration ecosystem, developer experience, and reliability. The competition has improved dramatically — PayPal’s API is finally respectable, Adyen is excellent at scale, Square is great for in-person — but for an online-first small business, Stripe is still the right default. Be aware of the effective-rate creep when you operate internationally. Be aware that Stripe’s ecosystem creates real lock-in over time. Don’t add value-added Stripe services until you genuinely need them. And keep an eye on processing volume — somewhere above $2 million, the calculus changes and it becomes worth talking to Adyen.

Henrik, thank you for the time.

Thanks. Write in if there are specific processor questions you’d like covered — we’ll be doing similar deep dives on Adyen, Klarna, and the Nordic-specific processors in coming pieces.