Stripe review for SaaS founders: what you actually pay for

By Gerald · 30 June 2026

Credit card on a clean white surface with soft lighting

I remember thinking Stripe was cheap. A flat 2.9% plus thirty cents per transaction. That was it, right?

Then I started building Flow and the monthly statements started telling a different story. Stripe is not one product. It is a stack of products, and each layer adds its own fee. The question is not whether Stripe is good. It is whether you understand what you are buying.

Stripe is the default payment processor for most SaaS companies for good reason. It is reliable, well-documented, and handles the hard parts of card processing. But the real cost of Stripe for SaaS is often higher than the headline rate suggests.

What Stripe actually charges

The base rate is 2.9% plus $0.30 per successful card charge for domestic transactions. International cards add another 1%. If a customer disputes a charge, that is a $15 fee. If you use 3D Secure for extra verification, that costs too.

These numbers were current on Stripe's pricing page in June 2026. They change, so check before you budget.

That base rate covers payment processing only. It does not cover subscriptions, tax calculation, invoicing, or marketplace splits. Each of those lives in a separate Stripe product with its own pricing.

Stripe Checkout: the good part

Stripe dashboard showing payment analytics — Stripe looks simple at first. The real cost shows up when you scale.

Stripe Checkout is the hosted payment page. You redirect your customer to Stripe, they enter their card, and Stripe sends them back. It handles the UI, validation, error states, and basic receipt emails.

For a new SaaS, Checkout gets you accepting payments in an afternoon. You do not design a form. You do not worry about PCI compliance beyond the basic SAQ-A. That is real value.

The downside is limited branding. You can add a logo and change some colors, but it is still clearly Stripe's page. For some products that is fine. For others, it breaks the trust built on a polished custom domain.

I used Stripe Checkout when Flow first started taking payments. It worked. Customers paid. I moved on to building the product instead of wrestling with card fields.

Stripe Billing: where subscriptions live

Stripe Billing adds subscription logic on top of payments. Trials, prorations, tiered pricing, usage-based billing. It is powerful and the API is clean.

Billing charges 0.5% on recurring payments. That does not sound like much until you do the math. On $10,000 in monthly recurring revenue, that is $50 per month on top of the card fees. At $50,000 MRR, it is $250 per month. At $200,000 MRR, you are paying $1,000 per month just for the billing layer.

For that money you get a solid system. It handles upgrade and downgrade prorations correctly. It sends invoice emails. It integrates with Stripe's customer portal so users can manage their own subscriptions.

The alternative is building your own billing logic. I have done that too. It is not fun. Dates, prorations, and edge cases around billing cycles will eat weeks of development time. Stripe Billing is expensive, but building it yourself is often more expensive.

Stripe Tax: the cost of compliance

Stripe Tax calculates sales tax, VAT, and GST based on your customer's location. It applies the right rate and can add it to the invoice automatically.

Tax costs 0.5% of the transaction. That is on top of processing and billing. So a subscription payment might flow through three Stripe fees: processing at 2.9% plus thirty cents, Billing at 0.5%, and Tax at 0.5%. On a $50 charge, that is roughly $2.45 in fees before any international card premium.

The value is real. Tax rules change constantly across jurisdictions. I do not want to track when Texas changes its software tax rule or when the EU updates its place-of-supply guidance. Stripe Tax does that for me.

But it is not a full tax filing service. It calculates what is owed. It does not file your returns. You still need an accountant or a separate filing tool.

Stripe Connect: when you pay others

Connect is for marketplaces and platforms. If your SaaS lets users sell things and you take a cut, Connect handles the split. It can pay out to connected accounts, hold funds, and manage compliance.

Connect pricing varies by setup. The standard model charges the platform the same processing rates, and connected accounts bear the cost. Express and custom accounts have different pricing tiers depending on volume and features.

I do not use Connect for Flow. Flow is a straightforward SaaS with one company and one set of customers. But if I ever added a marketplace feature, Connect would be the obvious path.

The real cost of simple payments

Here is the honest math for a typical SaaS at $30,000 MRR, mostly domestic cards, using Checkout, Billing, and Tax:

Processing: roughly $1,020 per month
Billing: $150 per month
Tax: $150 per month
Total: about $1,320 per month, or 4.4% of revenue

That is not ruinous. But it is not 2.9% either. And it grows linearly with your revenue.

At lower volumes, the flat $0.30 per transaction hurts more. A $10 monthly plan means the fixed fee is 3% on its own before the percentage cut. Stripe gets better value as your average transaction size grows.

What Stripe does well

Stripe's API is still the best in the industry. The documentation is clear. The webhooks are reliable. The error messages are helpful enough that you can usually debug without opening a ticket.

The developer experience matters. When a payment fails at 2 AM, you want logs you can read and a test environment that matches production. Stripe gives you that.

Stripe also handles edge cases most founders do not think about until they happen. Card account updater keeps expired cards working. Dunning management retries failed payments. The customer portal lets users update payment methods without your involvement.

Where Stripe falls short

Support is the biggest complaint I hear from other founders. At low volumes, you are mostly on your own. The chat bot is not great. Email responses can take days.

Pricing transparency is another issue. The headline rate is simple. The real stack of fees is not. You have to model your own costs carefully.

Stripe is also not a merchant of record. That means you are responsible for tax compliance, chargeback disputes, and regulatory issues in every country you sell to. If you want a merchant of record that handles all of that, you need Lemon Squeezy or Paddle instead.

Who should use Stripe

Stripe suits founders who want control and do not mind some complexity. If you have a technical team, if you want to customize your checkout flow, if you plan to build unusual pricing models, Stripe is hard to beat.

It also makes sense at scale. The per-transaction fees become a smaller percentage of revenue as you grow, and the reliability of the infrastructure matters more than the cost.

Who should look elsewhere

If you are a solo non-technical founder launching your first product, Stripe might be overkill. You will spend time on tax setup, webhook handling, and subscription logic that a merchant-of-record platform would handle for you.

If you sell globally and do not want to think about VAT, GST, or local tax rules, a platform like Lemon Squeezy or Paddle is probably a better fit. They charge higher fees but absorb the compliance burden.

How Flow uses Stripe

Flow uses Stripe for subscription billing. The integration handles monthly and annual plans, plan upgrades, and tax calculation through Stripe Tax.

It works. The webhook handling took a day to set up. The billing portal saved me from building a subscription management UI. I would make the same choice again.

But I am watching the monthly fees. At some volume it may make sense to evaluate alternatives. For now, the reliability and API quality are worth the cost.

Frequently asked questions

How much does Stripe cost? Stripe charges 2.9% plus $0.30 per domestic card transaction. International cards add 1%. Stripe Billing adds 0.5% for subscriptions, and Stripe Tax adds another 0.5% for automated tax calculation.

Is Stripe good for SaaS? Stripe is good for SaaS if you want a flexible API and do not mind managing tax and compliance yourself. It is less ideal if you want a merchant of record that handles everything for you.

What are Stripe's limitations? Stripe is not a merchant of record, so you handle your own tax compliance and chargeback risk. Support can be slow at low volumes. The real cost stacks up when you use Billing, Tax, and Connect together.

Does Stripe handle invoicing? Stripe Billing includes invoicing for subscriptions. You can also use Stripe Invoicing for one-off bills. Invoicing has its own pricing tier separate from card processing.

Is Stripe safe? Stripe is PCI Level 1 certified and handles card data securely. You can use Stripe Checkout to avoid handling card numbers directly on your servers.

My verdict

Stripe is the safe default for SaaS payments. It is not the cheapest, and it is not the simplest. But it is reliable, well-documented, and flexible enough to grow with you.

Just do the math on the full stack of fees before you assume it is cheap. The 2.9% headline is only the beginning.