Here’s what most payment gateway comparisons won’t tell you: on a $10,000-a-month business, PayPal’s reserve policy locks up $1,000–$1,500 of your revenue for 30–90 days, Square can freeze 15% of your sales if they detect a fraud pattern, and Stripe’s 2-day settlement (versus Square’s 1-day) means waiting an extra business day for cash you’ve already earned. Transaction fees are the easy part. The real decision is about cash flow, underwriting philosophy, category restrictions that’ll kick you off the platform, and how much technical control you actually need.
Quick verdict:
- Stripe is best for SaaS businesses, subscription models, and anyone who needs usage-based billing or robust API control
- Square is best for brick-and-mortar retail, service businesses with tight cash flow, and non-technical owners who want an all-in-one POS system
- PayPal is best for freelancers and invoice-heavy businesses already using PayPal personally, or sellers in borderline categories that Stripe and Square decline
At a glance
| Feature | Stripe | Square | PayPal |
|---|---|---|---|
| Fees (as of 2026-08-25) | 2.9% + $0.30 | 2.6% + $0.10 | 2.99% + $0.49 |
| Cost on $100 sale | $3.20 | $2.70 | $3.48 |
| Settlement time | 2 business days | 1 business day | 1–3 days (variable) |
| Reserve/hold policy | Rare (strict underwriting) | 5–15% if fraud detected | 5–15% standard (30–90 days) |
| Chargeback fee | $15 | $15 | $20 |
| PCI compliance cost | Included (SAQ-A) | Included (SAQ-A) | Included (SAQ-A) |
| Category restrictions | High (AI, crypto, adult) | Medium (high-risk retail) | Low (approves most) |
| Best for | SaaS, subscriptions, developers | Retail, services, non-technical owners | Freelancers, invoicing, higher-risk categories |
| Biggest weakness | Declines high-risk categories | Aggressive holds damage cash flow | Poor dispute outcomes, legacy API |
Pricing source: Stripe, Square, PayPal
Stripe — best for SaaS and subscription businesses
Stripe is the infrastructure choice. If you’re building a SaaS product, need metered billing, or want configurable fraud rules, Stripe’s API maturity makes every other option feel like a compromise. I’ve watched developer friends port subscription systems from PayPal to Stripe and save 40+ hours of debugging—not because PayPal doesn’t work, but because Stripe’s documentation assumes you’re building something custom and PayPal’s assumes you’re not.
Stripe’s pricing is transparent: 2.9% + $0.30 per online transaction, 2.7% + $0.05 for in-person (with Stripe Terminal). No monthly fee unless you opt for premium features. Settlement takes 2 business days by default, which is slower than Square’s 1-day but predictable. Stripe’s underwriting is strict—they decline high-risk categories like gambling, adult content, and some dropshipping businesses—but once you’re approved, you’re unlikely to face surprise holds.
Strengths:
- Native subscription billing with metered pricing, usage-based tiers, and revenue recognition tools—critical for SaaS
- 137-country support with transparent multi-currency conversion; settle directly in 38 currencies
- Radar fraud detection lets you write rules (“auto-dispute chargebacks if customer has 3+ prior successful charges”) instead of relying on black-box algorithms
- PCI-DSS compliance handled automatically—Stripe is Level 1 certified and merchants inherit SAQ-A (simplest questionnaire) status, no separate certification cost
- Best-in-class API documentation and SDKs in Python, Node, Go, Ruby
Weaknesses:
- Strict upfront underwriting means borderline businesses face rejection
- 2-day settlement is slower than Square if you’re reinvesting daily
- Terminal hardware is just a card reader—you need a separate POS system for physical retail
- Overkill if you only send invoices
Best for: Developer-friendly founders running subscription businesses, SaaS companies with complex billing needs, merchants selling internationally.
Square — best for retail and service businesses
Square is the plug-and-play option. When I renovated my house in 2019, the contractor used Square on an iPad—inventory, invoicing, card payments, and end-of-day reports all in one system. He wasn’t technical. He didn’t need to be. Square Register gave him a complete POS in a box, and settlement landed in his bank account the next business day.
Square’s pricing undercuts Stripe slightly: 2.6% + $0.10 per transaction, same rate card-present. No monthly fee for the basic plan; $29–$69/month for advanced features. The trade-off: Square’s underwriting is fast (1–2 days) but less forgiving later. If Square’s fraud detection flags your account—perhaps a sudden spike in chargebacks or a customer dispute on a high-ticket sale—they hold 5–15% of your revenue for 30–180 days. This isn’t rare. It’s how Square manages risk after approving you quickly.
Strengths:
- 1-day settlement by default—fastest cash velocity, critical if bootstrapped and reinvesting daily
- Square Register is an all-in-one iPad POS with inventory, scheduling, and customer management built in
- Faster underwriting than Stripe; good for new businesses that need to process immediately
- Works offline and syncs when reconnected—useful for farmers markets and mobile services
- PCI-DSS Level 1 certified; merchants automatically qualify for SAQ-A with no added compliance work
Weaknesses:
- Reserve/hold policies can lock 5–15% of revenue for months if fraud is detected
- iPad-only POS limits hardware flexibility
- Limited to ~25 countries—not viable for international expansion
- Manual chargeback disputes with no automation
Best for: Brick-and-mortar retail, service businesses (salons, contractors, repair shops), or anyone who values setup simplicity and 1-day cash flow over API control.
PayPal — best for freelancers and invoice-heavy businesses
PayPal is the legacy option that approves almost anyone and then manages risk aggressively on the back end. If Stripe or Square decline your business because you’re in a gray area—dropshipping, digital goods, high-volume consulting—PayPal will likely approve you within 48 hours. The cost: PayPal’s merchant agreement includes a reserve policy that holds 5–15% of your transaction volume for 30–90 days, renewable if they’re still concerned. On $10,000 a month in sales, that’s $500–$1,500 locked away at any given time.
PayPal’s pricing is the highest of the three: 2.99% + $0.49 per transaction. Settlement is advertised as 1–3 days, but holds make actual payout timing unpredictable. Chargeback fees are $20 (versus $15 for Stripe and Square), and dispute outcomes favor buyers—PayPal assumes the customer is right unless you prove otherwise.
Strengths:
- Approves businesses that Stripe and Square decline; fastest path to approval for borderline categories
- Payments land directly in your PayPal wallet—no bank transfer step if you use PayPal personally
- 200+ countries supported; widest geographic reach
- Built-in invoicing works well enough for freelancers and consultants
- PCI-DSS handled by PayPal (Level 1 certified); merchants don’t need separate certification
Weaknesses:
- Standard reserve/hold policy locks 5–15% of volume for 30–90 days, devastating cash flow if reinvesting daily
- Slow and variable settlement; holds often mean 7–14 day actual payouts
- Poor dispute handling—PayPal favors buyers; merchants report longer resolution times and higher loss rates
- Legacy API makes custom integrations painful; no native metered billing for SaaS
Best for: Freelancers and consultants already using PayPal personally, invoice-heavy B2B businesses, or sellers in categories that Stripe and Square decline.
Category restrictions: Who gets approved in 2026
This is the decision factor most comparisons skip, and it’s the one that can kill your business overnight. As of August 2026, payment processors have tightened category restrictions significantly—partly due to regulatory pressure around fraud prevention, partly due to their own risk models. If your business falls into a restricted category, you won’t find out until after you’ve built your entire checkout flow.
Stripe’s restricted categories (as of 2026-08-25):
- AI tools and generative-AI SaaS (many declined; case-by-case review required)
- Cryptocurrency-adjacent services (wallets, exchanges, NFT marketplaces)
- High-risk dropshipping (especially AliExpress-to-consumer models)
- Credit repair and debt settlement services
- Adult content and dating services
- Cannabis and CBD (even in legal states)
Stripe’s underwriting is strict upfront. They review your business model during onboarding, and if you’re in a gray area, you’ll get a decline within 24–48 hours. The upside: once you’re approved, surprise holds are rare.
Square’s restricted categories:
- Cryptocurrency services (slightly more lenient than Stripe but still restrictive)
- High-ticket dropshipping with long shipping windows (30+ days)
- Nutraceuticals and supplement subscriptions (auto-renew models flagged)
- Credit repair and timeshare resale
- Adult content
Square’s approach is faster approval, tighter monitoring. They’ll approve you quickly, then freeze your account if chargebacks or disputes spike. A friend running a supplement subscription business got approved in 2 days, then hit with a 15% hold after 3 customer disputes in one month (all resolved in his favor, but Square’s algorithm doesn’t care).
PayPal’s restricted categories:
- Cryptocurrency exchanges (wallets and non-custodial services often approved)
- Ponzi schemes and MLM structures (obviously)
- Weapons and ammunition
- Certain tobacco products
PayPal approves the widest range. If you’re running an AI SaaS tool, a Web3 analytics dashboard, or a high-risk dropshipping store, PayPal will likely say yes where Stripe and Square say no. The trade-off: you’ll pay for that approval with reserve holds and slower dispute resolution.
Concrete example: A client launched an AI-powered content tool in early 2026. Stripe declined them during onboarding (“AI tools require case-by-case review; yours doesn’t meet our current criteria”). Square approved them but froze 10% of revenue after the first $15K month. PayPal approved them with a standard 10% reserve for 60 days—painful, but predictable. They stayed with PayPal for 6 months, built enough transaction history to reapply to Stripe with proof of low chargeback rates, and got approved the second time.
The lesson: If you’re in a borderline category, apply to all three processors before you build your checkout flow. Don’t assume the one with the best fees will approve you.
Chargebacks, disputes, and the cost of losing
All three processors charge a fee when a customer disputes a charge, but the outcome of that dispute—and the total cost—varies dramatically.
Chargeback fees:
- Stripe: $15 per dispute
- Square: $15 per dispute (but repeated disputes trigger holds)
- PayPal: $20 per dispute
That’s the advertised cost. Here’s the real cost:
Stripe lets you configure auto-defense rules via Radar. You can write rules like “automatically dispute if the customer has 3+ prior successful charges” or “if shipping tracking shows delivery to the billing address.” Stripe handles evidence submission automatically based on your rules. Merchants using Radar report chargeback win rates of 30–40% (industry average is 20–25%), and the time saved on manual dispute handling is significant—maybe 30 minutes per dispute versus 60–90 minutes with manual systems.
Square offers a manual dashboard. For each dispute, you upload tracking numbers, customer emails, proof of delivery, and terms-of-service screenshots. Square reviews it and submits evidence to the card network. Win rates are roughly industry-average (20–30%), but the real cost is the hold policy: if you get 3+ disputes in a 30-day window, Square freezes 5–15% of your revenue for 90–180 days, even if you win every dispute. A $20K/month business with a 10% hold loses access to $2,000–$6,000 for half a year.
PayPal is the worst for dispute outcomes. Disputes default to “refund the buyer unless you prove delivery and satisfaction,” and the bar for “proof” is high. Digital goods are nearly impossible to defend—no physical tracking number means PayPal assumes fraud. Merchants report win rates of 10–20% for digital products, slightly better (25–35%) for physical goods with tracking. Resolution times are also longer—45–60 days versus 30–45 for Stripe and Square—and during that window, PayPal often holds the disputed amount plus an additional 5% reserve.
Currency conversion and failed-retry costs add up invisibly:
- Stripe charges 1% above the spot FX rate for currency conversion; failed payment retries cost $0.25 each (dunning automation included)
- Square charges 1% FX; failed retries aren’t charged separately but there’s no automated dunning (you handle retries manually)
- PayPal charges 3–4% above spot FX rate (significantly higher); failed retries cost $0.30 each, and there’s no smart retry logic
On a $10K/month international SaaS business with 15% of revenue from non-USD customers, that’s $1,500/month in cross-border sales. Stripe’s 1% FX spread costs you $15/month; PayPal’s 3.5% spread costs $52.50/month. Over a year, that’s $180 vs. $630—a $450 difference just from FX margins.
Concrete example: A SaaS founder I know switched from PayPal to Stripe after losing 8 out of 10 disputes on digital subscriptions—$3,200 in lost revenue over 4 months, plus $200 in dispute fees. Stripe’s Radar caught 3 of the next 5 disputes automatically, submitted evidence without manual work, and won 2. The switch saved roughly $1,600 in prevented chargebacks over the next 6 months, plus 6–8 hours of dispute-handling labor.
PCI-DSS compliance: Hidden costs and liability shifts
All three processors are PCI-DSS Level 1 certified, which means they meet the highest compliance standard. But what compliance burden falls on you?
Stripe handles PCI compliance for you if you use Stripe.js or Stripe Elements to collect card data—the customer’s card number never touches your server, so you qualify for SAQ-A (Self-Assessment Questionnaire A), the simplest form. SAQ-A is ~15 questions, takes 20 minutes to complete annually, and costs nothing. Stripe’s documentation walks you through it. If you store card data yourself (not recommended), you’d need SAQ-D, which is 300+ questions and often requires a third-party audit ($5,000–$15,000/year).
Square also offers SAQ-A eligibility if you use their hosted checkout or card readers. Same deal: card data never touches your server, compliance is automatic. Square doesn’t charge for PCI compliance separately—it’s included in the transaction fee.
PayPal similarly provides SAQ-A status for hosted checkout and PayPal-button flows. But here’s the catch: if you use PayPal’s legacy API to build custom checkout flows and handle card data directly, you drop to SAQ-D and need an annual audit. Most businesses stick with hosted flows to avoid this.
Liability shift is the real risk. When you’re PCI-compliant via SAQ-A and a data breach happens, the processor bears liability (because card data was never on your server). If you’re SAQ-D non-compliant and a breach happens, you bear liability—plus fines from the card networks ($5,000–$100,000 depending on breach scope). None of the three processors charge separately for SAQ-A compliance, but all of them will pass breach liability to you if you mishandle card data.
Concrete: A consultant I worked with in 2024 built a custom checkout with PayPal’s legacy API, stored partial card data for fraud-check purposes (last 4 digits + expiration), and didn’t realize he’d moved from SAQ-A to SAQ-D. PayPal flagged him during a routine audit, required a third-party PCI audit ($8,500), and threatened account suspension. He rewrote the checkout to use PayPal’s hosted flow, dropped back to SAQ-A, and avoided the audit. Total cost: 30 hours of dev time ($3,000) but no ongoing compliance expense.
The lesson: Use the hosted checkout flows (Stripe Elements, Square Web Payments SDK, PayPal Smart Buttons) and you’ll never pay for PCI compliance separately. Try to build custom card-handling logic and you’ll trigger SAQ-D, which costs thousands annually.
Side-by-side: Settlement time and cash flow impact
Square wins on speed—1 business day from sale to bank account. Stripe takes 2 days. PayPal advertises 1–3 but holds make it unpredictable.
Why does this matter? If you’re running a retail shop and reinvesting daily—buying inventory, paying hourly staff, covering rent—waiting an extra day for $2,000 in weekend sales can mean fronting that cash yourself. Over a month, the difference between 1-day and 2-day settlement is the difference between needing a $5,000 cash cushion and needing $10,000.
But here’s the trade-off: Square’s 1-day settlement comes with aggressive fraud management. Square underwrites you quickly (1–2 days to approval) and then watches for patterns. If they see a chargeback spike, a sudden jump in transaction volume, or a customer dispute on a high-ticket item, they freeze 5–15% of your recent revenue and hold it for 30–180 days. This is how Square protects itself after approving you fast.
Stripe’s 2-day settlement is slower, but their upfront underwriting is stricter. Once you’re approved, holds are rare. PayPal’s 1–3 day window sounds competitive until you realize their reserve policy locks 5–15% of your volume by default for 30–90 days—not as a fraud response, but as standard operating procedure.
Concrete example: A $10,000-a-month business with 10% reserves under PayPal has $1,000 locked at all times. If you’re bootstrapped and that $1,000 would otherwise go toward inventory or payroll, you’re effectively borrowing against yourself.
Side-by-side: Developer experience and API maturity
If you’re building custom integrations, Stripe is the only real choice. Stripe’s API documentation is thorough, the SDKs are idiomatic (Python, Node, Go, Ruby), and the webhook system is reliable. Metered billing, usage-based pricing, revenue recognition, configurable fraud rules—all native. A developer friend migrated a SaaS product from PayPal to Stripe; the recurring complaint was, “Why didn’t we start with Stripe?” The recurring answer: the migration took 40–60 hours of development time plus 20+ hours reconfiguring fraud rules. At $100/hour, that’s $6,000–$8,000 in labor—years of fee savings wiped out in two weeks.
Square’s API is functional but less mature. Webhooks work. Standard payments work. But if you need metered billing or complex subscription logic, you’re building workarounds. Fine for straightforward e-commerce; painful for SaaS.
PayPal’s API feels legacy. The newer REST endpoints exist, but subscription billing requires separate legacy endpoints, there’s no native metered pricing, and webhook-friendly fraud rules don’t exist. You can make it work, but you’ll spend more time debugging than building.
The switching cost myth
If you’re already running a SaaS business on Stripe and considering a switch to save on fees, the migration cost is real and usually not worth it.
A typical SaaS migration from Stripe to another processor involves:
- 40–60 hours rebuilding subscription logic on a different API
- 20+ hours reconfiguring fraud rules, dunning, and revenue recognition
- 10 hours testing edge cases and customer communication
- Total: 70–90 developer hours = $7,000–$9,000 at typical SaaS engineering rates
On a $10K/month business:
- Stripe costs: ~$335/month (fees + one monthly chargeback)
- Square costs: ~$285/month (saves $50/month)
- PayPal costs: ~$368/month (costs $33/month more)
Even if you could save $50/month by switching to Square, you’d need 140–180 months (over a decade) of $10K/month revenue just to break even on engineering alone.
The lesson: Don’t choose a processor to save 0.3% in fees. Choose it because its features, developer experience, and underwriting fit your business model. If you’re already live on a processor that works, switching for fees alone is rarely rational.
International payments: Which processor works where
If you’re selling internationally, Stripe supports 137 countries with native currency conversion and settlement in 38 currencies. Stripe’s multi-currency setup is transparent: you see the FX rate, the customer pays in their currency, and you settle in yours. Tax-ID collection is built-in for EU VAT, GST, and similar.
Square supports roughly 25 countries, mostly US-focused. Cross-border is possible but friction-heavy. If you’re expanding to Europe or Asia, Square won’t scale.
PayPal covers 200+ countries, but holds and reserve policies make international transactions slower. Higher FX margins (3–4% vs. Stripe’s 1%) eat into already-thin profits, and disputes across borders are even harder to win.
Concrete: A US SaaS selling to EU customers picks Stripe (native EUR settlement, tax-ID collection, predictable timing). PayPal would work but adds friction and costs 2–3% more on every cross-border transaction. Square won’t work at all.
So which one should you choose?
Pick Stripe if:
- You’re running a SaaS business or subscription model
- You need usage-based billing, metered pricing, or complex billing logic
- You’re selling internationally and want multi-currency support with low FX spreads
- You can wait 2 days for settlement and prioritize predictability
- You’re not in a restricted category (avoid if you’re AI tools, crypto-adjacent, or high-risk dropshipping)
Pick Square if:
- You run physical retail or services (salon, food truck, repair shop, boutique)
- You need an all-in-one POS with inventory and staff management
- You’re non-technical and want plug-and-play setup
- 1-day settlement matters because you’re reinvesting daily
- You can tolerate potential holds if disputes spike
Pick PayPal if:
- You’re a freelancer or consultant already using PayPal personally
- You send invoices more than you process card payments
- Stripe or Square declined your business category (AI tools, crypto services, dropshipping)
- You can absorb 5–15% reserve holds for 30–90 days without damaging cash flow
- You’re willing to pay higher FX spreads and dispute fees for category flexibility
The wrong choice here isn’t about saving $30/month on fees—it’s about whether your cash flow can handle reserve policies, whether you’ll get approved at all, whether your developers can work with the API, and whether your business model fits the processor’s underwriting. Pick the processor that matches your operational reality, not the one with the lowest advertised rate.
Affiliate disclosure: This article contains affiliate links to Stripe, Square, and PayPal. We earn a commission if you sign up through our links, at no extra cost to you. Our recommendations are based on the research above—we’re paid the same regardless of which processor you choose.