PayPal vs Stripe: The Real Cost Comparison for 2026

The fee comparison, done properly

Both companies publish their US rates openly, so there is no mystery here. Stripe is 2.9% plus 30¢ on a domestic online card. PayPal Checkout is 3.49% plus 49¢, dropping to 2.99% plus 49¢ when the customer pays with a card rather than a PayPal balance. Those are the numbers everyone quotes. What almost nobody does is show you how the fixed fee changes the answer depending on what you sell.

Look at the last column rather than the third. On a $1,000 invoice the two processors are 0.6 percentage points apart, which is a rounding error against everything else about running a business. On a $5 digital download they are 4.3 points apart, and PayPal is eating 13% of your revenue. If you sell low-ticket items, the fee difference is not a detail, it is your margin. If you sell high-ticket services, stop optimising the rate and pick on features.

There is one more tier worth knowing about. PayPal offers a micropayments rate of 4.99% plus 9¢, which sounds worse but is dramatically better below about $12. On a $3 sale, standard PayPal costs 59¢ and micropayments costs 24¢. You have to ask PayPal to enable it on your account, and most merchants who would benefit never find out it exists.

When the money actually arrives, which nobody tells you

This is the single most underreported difference between the two, and for a small business it can matter more than the rate. Stripe in the United States settles on a T plus 2 business day basis. That means a payment captured on Monday is available for payout on Wednesday. That part is fine. The part that catches people out is the first payout.

Stripe’s own documentation states that after your first live payment, the initial payout typically completes within 7 to 14 days, and can take longer depending on your industry and risk profile. So if you launch on a Monday and take $4,000 in your first week, that money is not in your bank on Wednesday. It might not be there for a fortnight. If you were counting on it to pay a supplier, you have a problem, and nothing in the signup flow warns you.

PayPal is the opposite. Money lands in your PayPal balance essentially instantly. You can spend it from the balance, or move it to your bank the next business day for free, or take an instant transfer for a percentage fee. For a business running tight on working capital, that immediacy is worth real money and it is the strongest practical argument for PayPal that has nothing to do with checkout conversion.

• Stripe US: T plus 2 business days settlement, first payout typically 7 to 14 days. ACH-funded payments settle in 4 business days, not 2.
• Stripe instant payouts: available for a fee of 1.5% of the payout, minimum 50¢.
• PayPal: immediate to balance, next business day to bank at no cost, or instant for a fee.
• Both: can and do apply rolling reserves to accounts they consider higher risk, which delays a percentage of every payout by up to 90 days or more.

Disputes, chargebacks and what each one costs you

Every top-ranking article about these two skips this section entirely, which is strange, because it is where the money goes wrong. Stripe charges $15 for each dispute you receive, and a further $15 if you respond to it manually. PayPal charges a $15 dispute fee and a $20 chargeback fee depending on how the case is routed. Those fees apply whether or not you win.

The process differs more than the price. PayPal handles disputes inside its own Resolution Center first, which means a customer who is annoyed often opens a PayPal dispute rather than going straight to their card issuer. That is genuinely useful, because a PayPal dispute is cheaper and more recoverable than a card network chargeback. PayPal’s Seller Protection, when you qualify, can cover you entirely on eligible unauthorised transaction and item-not-received claims.

Stripe’s dispute flow is more transparent and better instrumented, with Radar scoring every payment for fraud risk before it is captured and a clear evidence submission interface. Radar is included on standard pricing. But Stripe has no equivalent of Seller Protection. You win on evidence or you lose the money plus the fee.

The cross-border cost that quietly doubles your fee

If you sell internationally, this section is more important than the headline rate, and it is the one figure almost no comparison article surfaces. Both processors add a cross-border fee of 1.5% when the buyer and seller are in different markets. Fine, they match. The divergence is in currency conversion.

Stripe charges an additional 1% to convert. PayPal applies a conversion spread of around 4% on most transactions, sometimes 3%. That is a three point gap on every single converted sale, applied to the full transaction value. On a business doing $200,000 a year with half of it converted, that difference is roughly $3,000 annually, dwarfing anything you save or lose on the base rate.

Setup, developer experience and the thing Stripe is genuinely famous for

Stripe’s documentation is not just good for a payments company, it is good full stop. It is the reason developers push for Stripe even when finance would rather not switch. Test mode is a first-class environment, the API is coherent, webhooks are reliable, the client libraries are maintained, and the error messages tell you what is actually wrong. Building a working subscription checkout took us under three hours from empty repository to first successful charge.

PayPal’s developer platform is functional and much improved, but it carries two decades of accumulated history. There are multiple overlapping APIs, older integration paths still documented alongside newer ones, and it is easy to follow a guide that turns out to be for a product you are not using. The same subscription checkout took us closer to a full day, most of it spent working out which of PayPal’s products we were supposed to be using.

The flip side is that PayPal does not require a developer at all. You can generate a payment link, add a button to a site, or send an invoice, and be taking money in twenty minutes with no code. For a solo consultant or a side project, that is not a compromise, it is the entire point.

Account holds, reserves and the risk you are actually taking

Both companies reserve the right to freeze funds, impose a rolling reserve, or close your account. Both do it. Neither will tell you in advance where the line is, because publishing the criteria would tell fraudsters exactly how to stay under it. This is the part of the decision that the top ten results for this search do not mention at all, and it is the part that ruins people’s businesses.

PayPal has the older and louder reputation here, largely because of the 180-day hold that has generated a decade of angry forum posts. Stripe has a comparable process and terminates accounts in categories it considers restricted, sometimes with little notice. The honest position is that neither is safe if you are in a high-risk vertical, sell into a category either company restricts, have a sudden volume spike, or accumulate a chargeback rate above roughly 1%.

• Read the restricted businesses list before you integrate, not after. Both publish one. Supplements, CBD, firearms accessories, adult content, ticket resale, coaching and anything crypto-adjacent are common flashpoints.
• Do not let a single processor be a single point of failure. If all your revenue flows through one account, an account review is an existential event.
• Keep your chargeback rate visible. Both platforms surface it. Above 1% you are in monitoring territory with the card networks, not just the processor.
• Warn them before a spike. If you are about to run a launch that will 10x your volume, tell your processor first. Unexplained spikes trigger reviews.
• Keep a float. Assume you might lose access to a percentage of your balance for 90 days and price that risk into your cash planning.

Why running both is often the right answer

This gets treated as a cop-out conclusion, but the data supports it. A meaningful share of buyers, particularly outside the United States and particularly for higher-value purchases from unfamiliar brands, will abandon a checkout that only accepts a raw card form. PayPal’s button removes that hesitation. Meanwhile a meaningful share of buyers just want to type a card number and be done, and forcing them through a PayPal redirect adds friction and costs you 0.5 points of margin.

Modern checkouts can do both. Stripe supports PayPal as a payment method inside its own checkout, so you can take cards on Stripe rates and offer the PayPal button to the buyers who want it, all through one integration and one dashboard. Braintree, which PayPal owns, does the inverse. Either way you stop paying PayPal’s rate on customers who never wanted PayPal.

If you are choosing a stack rather than just a processor, it is worth looking at the wider field before you commit. Our roundup of Stripe alternatives covers merchant-of-record options like Paddle that handle global sales tax, and if you sell through a storefront our Shopify alternatives guide covers the platform fees that sit on top of processing.

So which should you choose?

Work through this table rather than trying to declare an overall winner, because there is not one. The right processor is a function of what you sell, how much it costs, where your buyers are, and whether you have a developer.

Whatever you pick, verify the numbers yourself before you build. Both companies publish current fees openly and both update them: Stripe on its official pricing page, and PayPal in its merchant fee schedule. Every figure on this page was checked against those two sources in August 2026, and the fixed fees in particular have moved more than once in the last three years.

One last piece of advice that has nothing to do with rates. Whichever you choose, set up a second processor before you need it. Not integrated and live, just approved and sitting there. The day your primary account goes into review is not the day you want to start a merchant application.