Stripe and PayPal are the two default payment platforms for web-based SaaS and indie software businesses, and the pricing looks superficially similar. Stripe charges 2.9% + $0.30 per successful card transaction; PayPal charges 3.49% + $0.49 for its commercial transaction rate. On a $20 subscription payment, Stripe takes $0.88 and PayPal takes $1.19 — a $0.31 difference that feels trivial. But the real cost gap between the two platforms only becomes visible when you look at the pricing curve across transaction sizes, factor in the operational realities of currency conversion, dispute handling, and account stability, and account for the customer segments each platform genuinely serves better. This article works through all of that with numbers, not vibes.

The Headline Rates — And What They Miss

Both platforms publish clean-looking domestic rate cards that assume a US-based business processing US-issued cards in US dollars. In that narrow scenario, the comparison is exactly what the pricing pages say:

Stripe wins on both dimensions. But those numbers don't answer the question SaaS founders actually care about: which platform costs less on the transactions I actually process?

The Break-Even Analysis Across Pricing Tiers

The percentage-plus-fixed structure means the two platforms' fee curves have very different shapes. At micro-transaction sizes, the fixed fee dominates and both platforms look expensive relative to the transaction. At larger transaction sizes, the percentage dominates and the fixed fee becomes negligible. Here's what the fees look like across the range of SaaS pricing that most independent businesses actually charge:

The pattern is unambiguous: Stripe is cheaper at every transaction size. On a $10 monthly subscription, PayPal costs 43% more per transaction than Stripe ($0.84 vs $0.59). On a $99 annual plan, the gap narrows to 24% ($3.94 vs $3.17). At scale — say, 1,000 monthly $20 subscriptions — the fee difference alone is $310/month, or $3,720/year. For a bootstrapped indie SaaS, that's more than the annual salary of a part-time contractor.

The Hidden Costs: Where the Real Gap Widens

The headline rates only apply to a specific transaction profile. Once you introduce international customers, currency conversion, disputes, and micropayments, the platforms diverge substantially.

International cards. Stripe adds 1.5% for international cards (cards issued outside your account country) plus another 1% if currency conversion is required. PayPal adds 1.5% for international commercial transactions plus 3–4% currency conversion spread built into the FX rate. For a US-based SaaS serving 30% international customers, Stripe's all-in international cost is roughly 5.4% (2.9% + 1.5% + 1%); PayPal's is closer to 8.5% once the FX spread is included. On $100K of international revenue, that's a $3,100/year difference.

Currency conversion. Stripe uses mid-market rates plus a fixed 1% conversion fee. PayPal uses its own inflated conversion rate (typically 3–4% worse than mid-market) and does not itemize the spread as a separate fee — it's hidden inside the exchange rate you receive. This makes PayPal look artificially cheaper on invoices while being materially more expensive in practice. Multi-currency SaaS businesses often discover this only after year one, when they reconcile Stripe payouts to PayPal payouts and find the “equivalent” revenue produced dramatically different USD deposits.

Chargebacks and disputes. Stripe charges $15 per chargeback (waived if you win the dispute). PayPal charges $20 per chargeback plus keeps the transaction fee even if you win. PayPal's dispute resolution process is notoriously buyer-favorable — many merchants report win rates below 30%, versus 60%+ on Stripe with proper documentation. For a SaaS with a 0.5% chargeback rate, this shifts annual cost by another 20–40 basis points of gross revenue.

Micropayment pricing. PayPal offers a specific “micropayments” tier of 4.99% + $0.09 for transactions under $10, which is genuinely cheaper than Stripe for very small purchases (below roughly $5). Stripe does not offer an equivalent tier without a custom deal. For a business selling $1–$3 in-app top-ups at high volume, PayPal micropayments is one of the few scenarios where PayPal is unambiguously cheaper.

Account Stability: The Cost You Can't Model

Every SaaS founder eventually hears the horror story: PayPal froze the account, held 30% of the balance for 180 days, and offered no explanation beyond a generic risk-review email. These stories are not folklore — PayPal's account holds and rolling reserves affect a meaningful minority of merchants, particularly those in high-risk categories (digital goods, subscription services, cross-border sales) or those experiencing rapid revenue growth. The financial impact is severe: a 30% rolling reserve on $50K/month in revenue means $15K/month tied up for six months, or $90K of working capital effectively frozen.

Stripe is not immune to account issues — it also freezes funds and closes accounts, particularly for merchants who fail its Know Your Customer (KYC) verification or trigger fraud model heuristics. But Stripe's reputation for communication and predictability during risk reviews is materially better than PayPal's among indie developer communities. This is a soft factor that doesn't show up in fee tables but shapes long-term platform selection for any business planning to scale past $50K/month.

Where PayPal Still Wins

Despite Stripe's pricing and stability advantages, PayPal remains the correct choice in specific segments — and dismissing it entirely leaves money on the table.

Customer preference in certain regions. PayPal has dominant checkout share in Germany, the Netherlands, and much of Latin America. A SaaS targeting German small businesses that removes PayPal from checkout can see conversion rates drop 15–30% overnight. The extra 0.6% per transaction is worth paying if it's the difference between a sale and no sale.

Consumer trust for one-time purchases. First-time buyers of digital goods (indie games, ebooks, courses) often trust PayPal more than they trust an unfamiliar merchant handling their card directly. If your customer acquisition depends on cold traffic converting on first visit, PayPal-as-option (not PayPal-as-only) is standard practice — even Stripe-first businesses typically offer PayPal as a secondary checkout option specifically for the trust anchor.

Micropayment volume. As noted above, PayPal's dedicated micropayments tier (4.99% + $0.09) is cheaper than Stripe for transactions under $5. High-volume, low-ticket businesses genuinely benefit.

Practical Recommendation for Independent SaaS

For the typical bootstrapped SaaS charging $10–$99/month, targeting a global customer base, and prioritizing account stability, the pragmatic default is: Stripe as primary, PayPal as an optional secondary checkout. This captures Stripe's superior economics on the bulk of transactions while preserving conversion on the segment of customers who prefer PayPal specifically. The engineering overhead to support both is modest — Stripe's and PayPal's SDKs are both mature, and most modern checkout libraries (or Stripe's own Checkout link) can present both options side-by-side.

If you're just starting out and want to launch with one platform, Stripe is the safer default across almost every axis: lower fees, more predictable payouts, better documentation, cleaner dispute handling, and better developer tooling. Only pick PayPal-first if your target audience is specifically PayPal-heavy (mainland Germany, informal marketplaces, high consumer-trust dependency).

Model Your Own Scenario

The simulator on the home page lets you toggle between Stripe and PayPal as your platform, set a specific transaction count and unit price, and see the exact commission impact on your revenue waterfall across the countries you sell into. Try setting Platform to Stripe with your typical monthly subscription price and transaction count, then switch to PayPal — the Commission line updates in real time. On any non-trivial revenue base, the difference is usually much larger than founders expect.