PayPal

PayPal is a payments network with a consumer wallet at the front of it. That single fact explains almost everything about where it wins and where it frustrates. Merchants adopt PayPal less for its developer tooling than for the buyers who already have an account, a stored balance and a familiar dispute process — and who are more willing to complete a checkout they recognise.

What you are actually buying

• Wallet checkout — the PayPal button, where buyers pay from a stored balance, linked bank account or card without re-entering details.
• Card acquiring — advanced checkout options that accept cards directly on your site, including PayPal-owned Braintree for teams wanting a fuller gateway API.
• Invoicing and payment links — no-code ways to request money, widely used by freelancers and service businesses.
• Payouts — sending money to sellers, contractors and affiliates, including cross-border.
• Buy now, pay later and alternative methods — surfaced through the same integration in supported markets.

The conversion argument

The strongest case for PayPal is behavioural rather than technical. A buyer who does not want to type a 16-digit card number into an unfamiliar site will often still pay through a wallet they trust. That is why PayPal most commonly earns its place as an additional payment method alongside a primary card processor rather than as a replacement for one.

We deliberately publish no uplift figure here. Vendor-quoted conversion improvements are not independently verifiable, and the honest test is your own: run PayPal as a secondary method and measure the effect on your completed-checkout rate.

Developer experience

PayPal's integration surface is broader and less coherent than a single-purpose gateway, because it has accumulated products, SDKs and legacy APIs over a long history. Current documentation is serviceable and the JavaScript SDK covers the common cases well, but teams routinely lose time working out which of several overlapping products they should be using. Braintree exists partly to answer that: it is the developer-first path inside the same corporate family.

Disputes, holds and account risk

This is where PayPal deserves the most careful reading, because it is the most common source of merchant complaint. PayPal operates buyer protection, and the resolution process is designed around it. Funds can also be held or reserved on risk grounds, particularly for new accounts, high-growth accounts, pre-order and long-fulfilment models, and categories PayPal treats as higher risk.

None of that is hidden — it is in the user agreement and the acceptable use policy — but it is under-read. If your business model involves long delivery windows, deposits or digital goods, read those documents before you make PayPal your only way to get paid, and keep a second processor configured. Concentration risk in payments is a genuine operational exposure, not a theoretical one.

Pricing

PayPal publishes per-transaction merchant fees that vary by country, product, transaction type, currency conversion and cross-border status, with additional charges for chargebacks and some payout methods. We do not reproduce rates here because the fee that matters is your blended one — domestic versus international, currency-converted versus not. Check PayPal's official fees page for your market.

Where PayPal fits

• Consumer ecommerce adding a recognised wallet next to card payments.
• Freelancers and small service businesses who need to invoice and get paid without an integration.
• Cross-border sellers whose buyers already hold PayPal accounts.
• Marketplaces and creator platforms needing straightforward payouts to many recipients.

Where it does not fit

• As a sole processor for businesses with long fulfilment windows or deposit-based models — read the reserve and hold policies first.
• Complex subscription billing, where a billing-first platform models plan changes and dunning far better.
• In-person retail and hospitality as a primary channel.
• Teams that want one clean, modern API surface rather than a family of overlapping products.

Independent verdict

PayPal earns its place through buyer familiarity, and for most consumer ecommerce that is a real commercial advantage worth paying for. As a complement to a primary card processor, it is close to a default.

As your only route to revenue it is a riskier choice than merchants expect, and the reasons are in the policies rather than the product. Offer it, measure it, and keep a second processor live.