If you run a subscription business, a membership site, a SaaS, a recurring service, or any kind of billing that happens more than once per customer, you will end up choosing between Stripe, PayPal, and Square. There is no fourth option worth considering at small-business scale in 2026. Authorize.Net is for legacy enterprise. Adyen is for processing volume that makes your accountant nervous. Braintree is just Stripe with extra steps.
This guide compares the three realistic choices on the dimensions that actually matter when you are picking a recurring billing platform: per-transaction fees, international card support, dunning UX (the work the processor does to recover failed payments for you), dispute handling, developer ergonomics, and the cost of leaving if you change your mind. The goal is to give you a decision framework that survives contact with real customer data, not a feature checklist copied from each company's marketing site.
The cheapest processor on paper is rarely the cheapest in practice. The difference is almost always dunning quality and dispute handling, not the headline rate.
The setup: what each processor actually charges
Let me get the sticker price out of the way first. All three publish current rates, but the published rate is what you pay on the simplest possible transaction. Real recurring billing is never the simplest possible transaction.
| Processor | US card rate | International card | Amex surcharge | Monthly fee | Chargeback fee |
|---|---|---|---|---|---|
| Stripe | 2.9% + 30¢ | +1.5% | 0¢ (same rate) | $0 | $15 |
| PayPal (PayPal Checkout + Subscriptions) | 3.49% + 49¢ | +1.5% | 0¢ (same rate) | $0 | $20 |
| Square (Subscriptions API) | 2.9% + 30¢ | +1.5% | 0.5% (Amex surcharge in addition to base) | $0 (Subscriptions API free; Square subscriptions dashboard $0; fees apply elsewhere) | $15 |
Sources: Stripe US pricing, PayPal US business pricing, Square processing rates.
A few things this table hides that matter at small-business scale:
- Stripe and Square both charge 2.9% + 30¢ on US cards. PayPal charges 3.49% + 49¢. On a $19/month subscription, that is roughly $0.34 vs $0.95 in processor fees per month per customer. PayPal costs about 60% more per transaction at this price point. At $99/month, the gap is roughly $0.34 vs $1.74, about 5x more expensive. PayPal's fee structure punishes small transactions harder than large ones because the fixed fee is larger relative to the percentage.
- International cards add 1.5% across the board. If you sell globally, you are paying the same premium for the same reason everywhere. The question is what the processor does to actually accept those cards (some currencies, some payment methods) and to convert them into your home currency cheaply.
- Square's Amex surcharge is unusual. Most processors dropped Amex surcharges years ago because merchants hated them. Square charges an extra 0.5% on Amex on top of the base rate. If you have any meaningful Amex volume, that adds up fast.
Recurring billing primitives: what each platform actually gives you
The headline rate is the first filter. The second filter is what each platform gives you to manage recurring billing, dunning, and the inevitable failed payments.
<figure> <img src="/blog/img/stripe-vs-paypal-vs-square-recurring-billing-2026-2.webp" alt="Vintage robot comparing three payment processor devices side by side" /> </figure>Stripe Billing (the developer-first default)
Stripe's billing product is what every other processor benchmarks against. The primitives you get out of the box:
- Subscriptions API. Create a customer, attach a payment method, create a subscription with a price ID, attach multiple prices (metered, tiered, usage-based), prorate on upgrade, prorate on downgrade, schedule a cancellation at period end. The API surface is the deepest of the three.
- Smart Retries. Stripe's machine-learning retry engine, built on billions of historical payment attempts, picks retry timing based on the failure reason, the customer's bank, and the time of week. Published recovery rate is around 40-50% of retried charges (Stripe Smart Retries documentation).
- Stripe Invoicing. Send one-off invoices, recurring invoices, quote-to-invoice flows. Built on the same primitives as Subscriptions.
- Customer Portal. Hosted page where your customers can update their card, switch plans, view invoices, cancel. Customizable branding. This single feature saves most small businesses from building a "billing settings" UI.
- Tax. Stripe Tax calculates sales tax, VAT, and GST for you. The fee is 0.5% of the transaction volume Stripe processes.
The catch: Stripe assumes you have a developer. The dashboard is functional but not the primary interface. If you are a non-technical founder, you will need to either use a no-code layer (Outseta, Memberstack, SureCart) on top of Stripe, or pay someone to set up your subscription logic.
PayPal Subscriptions (the "people already trust us" option)
PayPal's recurring billing has improved a lot since the early 2020s, but it still feels like a different product than Stripe's. The primitives:
- Subscriptions API. Create a plan, create a subscription, attach a customer. The API is smaller and less flexible than Stripe's. No native usage-based billing without a third-party layer.
- Smart Subscribe Buttons. PayPal's hosted button maker that lets you add recurring billing without writing code. This is PayPal's real advantage for non-technical sellers.
- Vault and reference transactions. Store a payment method against a customer, charge it later. This is how you build anything custom on top.
- No real dunning. This is the biggest gap. PayPal retries failed payments 4 times over 4 days, then cancels the subscription. There is no customizable retry schedule, no recovery email automation beyond PayPal's own template, and no equivalent of Stripe's Smart Retries machine-learning model. If a charge fails on a $9/month subscription, the customer is gone faster than on Stripe.
The catch: PayPal's fees are higher, the API is thinner, and the recovery tooling is weaker. The reason to pick PayPal is that your customers already have PayPal accounts and trust the brand, especially internationally. In some markets (Germany, parts of Southeast Asia, Latin America) PayPal conversion is materially higher than Stripe because of brand trust.
Square Subscriptions (the in-person-first option)
Square started as a card reader for coffee shops and grew into a full POS system. Subscriptions were added later and are an obvious fit if your business is mostly in-person plus a small recurring component (a monthly wine club, a personal training package, a recurring service contract).
- Subscriptions API. Create a plan, attach a customer, charge the saved card. Simpler than Stripe's API, comparable to PayPal's.
- Square Dashboard. Square's UI is the best of the three for non-technical operators. If you have a brick-and-mortar business that also does recurring billing, the integrated dashboard is genuinely better than running Stripe for subscriptions and a separate POS.
- Dunning. Square's built-in dunning is similar to PayPal's: retry on the standard schedule, send a templated email, cancel after a fixed number of attempts. No machine-learning retry timing, no customizable retry rules.
- Square Invoices. Send recurring or one-off invoices with a hosted payment page.
- Card-on-file rates. Square does not surcharge card-on-file or recurring transactions. The published rate is the rate.
The catch: Square's API is not where Stripe's is. If you are a software company or a SaaS, Square will feel limiting fast. Square is also US/Canada/Australia/UK/Japan/France focused. If you sell globally outside those markets, Stripe or PayPal is the realistic choice.
The decision matrix: which processor for which business
Here is the framework. Answer these questions in order and the right answer falls out.
Are you a SaaS, software company, or any business that needs a billing API?
Pick Stripe. PayPal and Square both have APIs, but Stripe's is the deepest, the best documented, and the most widely supported by third-party tools (Stripe Atlas, Outseta, Memberstack, SureCart, Chargebee, Recurly, all default to Stripe). PayPal's API will work but feels like an afterthought. Square's API will work for simple cases and break down fast on anything complex (metered usage, proration, plan changes mid-cycle).
Are you a non-technical service business that sells recurring services (gym, salon, dog walker, consultant)?
Pick Square. The dashboard is the best of the three for non-technical operators. The recurring billing is integrated with the POS, the appointment calendar, and the customer records. If your customers pay you in person and online, Square handles both with one dashboard.
Are you a content creator, course seller, or membership site that wants minimal infrastructure?
Pick PayPal. The smart subscribe button lets you set up recurring billing in five minutes with no code. Your customers may already trust PayPal more than they trust a checkout form on your domain. The fee premium is real, but for low-volume creators the simplicity is worth more than the savings.
Do you sell internationally, especially in markets where PayPal has stronger brand trust than Stripe?
Consider PayPal. Specifically Germany, Austria, parts of Latin America, and parts of Southeast Asia. In these markets, PayPal conversion can be 20-30% higher than Stripe because customers already have accounts and trust the brand. If a meaningful chunk of your revenue is from one of these markets, the conversion lift can pay for the higher per-transaction fee.
Are you a high-volume subscription business that needs the best dunning and the lowest effective fee?
Pick Stripe. Smart Retries recovers more failed payments than PayPal's or Square's fixed schedule, and the API lets you layer your own dunning email sequence on top. If your average revenue per user is over $50/month, Stripe's fee advantage plus its dunning advantage compounds meaningfully.
Dunning quality: where the real money is
The fee comparison above is the wrong place to look if you want to optimize your subscription business. The real money is in dunning, the recovery rate on failed payments.
<figure> <img src="/blog/img/stripe-vs-paypal-vs-square-recurring-billing-2026-3.webp" alt="Vintage robot reviewing subscription billing performance charts in a home office" /> </figure>The published recovery rates from the processors themselves:
- Stripe Smart Retries: 40-50% recovery rate on retried charges. Stripe also publishes a "recovery uplift" figure comparing Smart Retries to a naive retry schedule. The published uplift is around 6-12 percentage points over a fixed retry schedule, depending on industry and price point (Stripe Smart Retries documentation).
- PayPal: No published recovery rate. Based on community benchmarks and processor comparisons, PayPal's fixed 4-retry-over-4-days schedule recovers somewhere around 30-35% of failed payments.
- Square: No published recovery rate. Square's retry schedule is similar to PayPal's, with around 30-35% recovery based on community benchmarks.
The reason this matters: if you process $100,000/month in subscriptions and have a 5% involuntary churn rate (failed payments that lead to cancellation), you are losing $5,000/month to failed payments before any recovery effort. With a 45% recovery rate, you recover $2,250/month. With a 30% recovery rate, you recover $1,500/month. That is a $750/month difference on $100K of monthly volume, which dwarfs any difference in the headline transaction fee.
For a deep dive on building a custom dunning sequence on top of Stripe (the four-part workflow: webhook listener, state machine, email sequence, escalation), see our Stripe Payment Failure Recovery guide.
Dispute handling: the silent fee most businesses miss
Chargebacks are the dark side of subscription billing. Every chargeback costs you the transaction amount, the chargeback fee, and the time spent responding to the dispute. The processor you pick affects how painful this is.
| Processor | Chargeback fee | Win rate (industry benchmark) | Dispute evidence portal | Network-level visibility |
|---|---|---|---|---|
| Stripe | $15 | 30-40% | Stripe Dashboard + Verifi/CDRN early warnings | Full Visa/MC dispute data via API |
| PayPal | $20 | 25-35% | PayPal Resolution Center | Limited; mostly PayPal-mediated |
| Square | $15 | 30-40% | Square Dashboard | Full Visa/MC dispute data via API |
Sources: industry benchmarks aggregated from Midigator chargeback statistics, Stripe dispute documentation, and PayPal seller protection terms.
A few details this table hides:
- PayPal's chargeback fee is the highest ($20 vs $15) and its published win rate is the lowest. The reason is that PayPal disputes often go through PayPal's Resolution Center first, which has a different set of evidence rules than the card networks. PayPal's process is faster but harder to win.
- Stripe and Square both use the card-network dispute system directly. Verifi and CDRN are network-level pre-dispute programs that notify you before a chargeback becomes a formal dispute, giving you a chance to refund the customer before the chargeback fee hits. Both Stripe and Square integrate with these programs. PayPal's integration is weaker.
- For sellers with high dispute volume (more than 0.5% of transactions), Stripe or Square's network-level visibility is worth real money. Catching a dispute early and refunding proactively avoids the $15 fee entirely.
Migration: what happens if you pick wrong and need to switch
The most underestimated factor is the cost of switching. Subscription data, especially customer payment methods, saved cards, and historical invoices, is hard to migrate cleanly.
- Stripe has the best migration tooling in the industry. Stripe's "migration suites" let you import subscriptions from PayPal, Braintree, Recurly, and Chargebee with a single API call. The reverse (export from Stripe to anyone else) is also well supported because Stripe's data model is the de facto industry standard.
- PayPal has migration tools but they are thinner. You can export subscriptions as a CSV, but you cannot export saved payment methods (they are PayPal vaulted, not raw card data, for PCI reasons). This means your customers have to re-enter their cards after migration.
- Square has decent migration tooling for moving into Square but limited tooling for moving out. The export is CSV-based and you lose saved cards, same as PayPal.
The bottom line: if you think you might switch processors in 18 months, pick Stripe now. The migration cost out of PayPal or Square is a real barrier, and Stripe is the only processor where the import/export tooling is symmetric.
The bottom line
The cheapest processor on the headline rate is not the cheapest in practice. The right answer depends on your business:
- Software, SaaS, any business that needs a billing API: Stripe. The API depth, the dunning tooling, and the migration symmetry make it the default for any recurring billing product.
- Service business, brick-and-mortar, non-technical operator: Square. The integrated dashboard is better than the alternatives for businesses where billing is one of many operational concerns.
- Creator, course seller, low-volume recurring sales: PayPal. The smart subscribe button is the simplest way to ship recurring billing without code, and your customers may already trust the brand.
- Global business, especially in markets where PayPal dominates: Consider PayPal for those markets specifically, even if Stripe is your primary processor elsewhere. You can run both in parallel.
Whatever you pick, build the dunning workflow on day one. The difference between a 45% recovery rate and a 30% recovery rate is more revenue than you will ever find by switching processors. For a practical guide to shipping that workflow on Stripe, see our payment failure recovery automation guide. For a broader comparison of automation platforms that can wire your billing to the rest of your stack, see our Zapier vs Make vs n8n comparison.
The right billing processor is the one you can stop thinking about after you set it up. Pick the one that fits your business, build the dunning workflow, and move on to the part of your business that actually needs your attention.