PayPal

What Is PayPal?

PayPal is a global digital payments platform and online wallet that lets people and businesses send, receive, and accept money over the internet. The direct answer to the most common question is that PayPal is one of the most recognized and widely accepted online payment methods in the world, and its core advantage for merchants is consumer trust: shoppers already have PayPal accounts and often feel safer checking out with a familiar wallet.

PayPal traces its roots to 1998 and the merger that formed the modern company, and it has reported well over 400 million active consumer and merchant accounts across more than 200 markets in its own investor disclosures. Technology-detection surveys from sources such as BuiltWith consistently rank PayPal among the most-detected payment technologies on the web, reflecting how commonly stores add a PayPal button alongside other checkout options. Exact figures vary by source and methodology, so treat any single statistic with caution; the consistent finding is that PayPal is a near-ubiquitous presence in online checkout.

Unlike a developer-first processor that owns a fully custom card flow, PayPal is best understood as both a payment processor and a consumer wallet. Customers can pay from their PayPal balance, a linked bank account, or a card, frequently without re-entering details, which is why offering PayPal is so often associated with higher checkout conversion among shoppers who prefer it.

How PayPal Works

PayPal sits between a merchant and the customer's funding source, and its defining trait is that much of the sensitive flow happens on PayPal's own infrastructure rather than the merchant's.

Modern integrations use the PayPal JavaScript SDK, loaded from https://www.paypal.com/sdk/js, which renders PayPal's Smart Payment Buttons on the merchant's page. Supporting assets (images, logos, and some scripts) are served from paypalobjects.com. When a shopper clicks the PayPal button, the experience typically opens a PayPal-hosted window or in-context overlay where the customer logs into their PayPal account and approves the payment. Because authentication and funding-source selection happen on PayPal's domain, the merchant never handles the customer's PayPal credentials or, in most cases, their raw card details.

A typical purchase lifecycle works like this. The merchant's page loads the PayPal SDK and renders a button. On click, the merchant's server (or the SDK) creates an order with PayPal's Orders API, and the customer is taken into PayPal's hosted approval flow to log in and confirm. After approval, control returns to the merchant, and the server captures the payment through PayPal's API, finalizing the charge. PayPal then settles funds into the merchant's PayPal account, and the merchant can react to the result and to asynchronous events through Instant Payment Notification (IPN) or webhooks, PayPal's server-to-server callbacks for events like completed payments, refunds, and disputes.

PayPal exposes the global paypal object in the browser once the SDK loads; the buttons themselves render inside an iframe on PayPal's domain, which is why styling is constrained to documented options. PayPal also sets cookies to manage sessions, fraud signals, and continuity, including a ts_c cookie among others. From a detection standpoint, the recurring theme is that PayPal's presence is signaled by the SDK script, the paypalobjects.com asset domain, the paypal JS global, the buttons iframe, and PayPal cookies, with the actual payment approval taking place on PayPal-controlled pages.

Beyond the standard checkout, PayPal offers Smart Payment Buttons that can also surface card fields and alternative methods, Pay Later installment options in eligible markets, Venmo as a funding choice in the US, and invoicing tools that send a hosted payment link. In all of these, the architectural pattern is similar: PayPal hosts the sensitive parts of the flow, and the merchant integrates through buttons, redirects, and server-side API calls plus webhooks.

How to Tell if a Website Uses PayPal

PayPal leaves clear fingerprints in scripts, asset domains, iframes, the DOM, cookies, and redirects. Here are the signals to look for and the tools that surface them.

Signals in the page and network

• PayPal SDK script. The strongest signal is a <script> loading https://www.paypal.com/sdk/js (often with a client-id query parameter). Older integrations may load checkout.js. Its presence almost always indicates a PayPal integration.
• paypalobjects.com assets. Images, logos, and scripts served from www.paypalobjects.com are characteristic of PayPal buttons and badges.
• The paypal global. Once the SDK loads, the browser exposes a global paypal object. In the DevTools Console, typing paypal or window.paypal returns it.
• PayPal buttons iframe. Smart Payment Buttons render inside an iframe whose src points to PayPal's domain. Inspecting the button area in the Elements panel reveals this iframe.
• Cookies. Look for PayPal cookies such as ts_c (and other ts*/PayPal-set cookies) in the Application/Storage tab.
• Hosted-flow redirects. Clicking a PayPal button opens a window or navigates to paypal.com, a definitive signal that the checkout uses PayPal.

Tools to confirm it

Tool	What you do	What it reveals
View Source	Open the page source in your browser	A <script src="https://www.paypal.com/sdk/js..."> tag and paypalobjects.com asset URLs
Browser DevTools (Console)	Type paypal or window.paypal	The global paypal object confirms the SDK is loaded
Browser DevTools (Elements)	Inspect the PayPal button area	A buttons iframe served from paypal.com
Browser DevTools (Network/Application)	Watch requests and cookies	Loads from paypalobjects.com, PayPal cookies such as ts_c
curl -I	Run curl -I https://example.com	Header hints, though most PayPal signals are client-side and may not appear here
Wappalyzer / BuiltWith	Run the extension or look up the domain	Flags PayPal in the payment-processor category

Because PayPal's button and approval flow run in the browser and on PayPal's domain, DevTools is more reliable than curl for detection. For step-by-step methods, see our guides on how to find out what payment processor a website uses and how to find out what e-commerce platform a website uses.

Key Features

PayPal offers a broad set of consumer and merchant payment capabilities.

• PayPal Checkout (Smart Buttons). One-click-style buttons that let customers pay with their PayPal balance, linked bank, or card through a hosted flow.
• Consumer wallet. Hundreds of millions of existing accounts that customers reuse across merchants without re-entering details.
• Pay Later. Installment and buy-now-pay-later options in eligible markets, surfaced at checkout.
• Venmo (US). Venmo as a funding option for US shoppers, integrated through the same SDK.
• Invoicing. Hosted invoices with payment links for service businesses and freelancers.
• Buyer and seller protection. Programs that cover eligible transactions, a key driver of consumer trust.
• Global reach. Support for many currencies and markets, with built-in currency conversion for cross-border sales.
• APIs and webhooks. Orders API, IPN, and webhooks for server-side order creation, capture, and event handling.

A few capabilities stand out. Buyer protection is central to PayPal's value proposition and is a major reason shoppers trust the button. Smart Payment Buttons can dynamically present the most relevant funding options, including Pay Later and local methods, based on the buyer and market. And the hosted approval flow means merchants offload the most sensitive parts of authentication and funding selection to PayPal, simplifying compliance.

Pros and Cons

PayPal's strengths and trade-offs both stem from its role as a trusted consumer wallet layered on top of payment processing.

Pros

• Exceptional consumer trust and brand recognition that can lift conversion.
• Customers can pay without re-entering card details using existing PayPal accounts.
• Quick to add to most stores and platforms with minimal development.
• Broad global acceptance across many markets and currencies.
• Buyer and seller protection programs for eligible transactions.
• Additional options like Pay Later and Venmo broaden payment choice.

Cons

• Per-transaction fees can be higher than some alternatives, and currency conversion adds cost.
• Limited control over the checkout look and feel because the flow is PayPal-hosted.
• Funds can be subject to holds, reserves, or account reviews, especially for newer or higher-risk sellers.
• Dispute and chargeback handling runs through PayPal's processes and policies.
• The redirect/overlay flow is less seamless than a fully embedded custom checkout.
• Heavy reliance on client-side SDK and hosted pages means integrations must handle approval and capture steps carefully.

PayPal vs Alternatives

PayPal competes with other payment processors and wallets. The right choice depends on whether you prioritize consumer trust, checkout control, or developer flexibility.

Provider	Primary model	Strength	Best for
PayPal	Hosted buttons + consumer wallet	Consumer trust and recognition	Stores wanting a familiar, high-trust buy button
Stripe	Developer-first APIs + hosted checkout	Developer experience, breadth of products	SaaS, marketplaces, custom checkouts
Square	Integrated POS + online payments	Unified online/offline commerce	Retail and hospitality with physical and online sales
Apple Pay / Google Pay	Device-based wallets	Fast mobile checkout	Mobile-heavy stores adding express wallets
Klarna / Afterpay	Buy-now-pay-later	Installment conversion	Stores targeting installment-friendly shoppers

If you want to compare against a developer-first processor that owns the full card flow, see our profile of Stripe, which covers the trade-offs in depth.

In short: choose PayPal when consumer trust at the buy button and reuse of existing wallets matter most; choose Stripe when you are building a custom checkout and value developer experience; choose Square when you blend physical and online sales; and choose device wallets or BNPL providers as complementary express or installment options. The most instructive comparison is PayPal versus Stripe, because many stores offer both. PayPal acts as the recognizable wallet that reassures hesitant shoppers and lets them pay without re-entering details, while Stripe acts as the developer-controlled card engine behind a bespoke checkout. Offering both captures shoppers at different points of trust and preference, which is why the combination is so common.

Use Cases

PayPal fits a recognizable set of scenarios.

• Trust-sensitive checkouts. Stores where offering a familiar, protected payment method increases the likelihood that hesitant shoppers complete a purchase.
• International selling. Merchants reaching customers across many markets and currencies without building complex payment infrastructure.
• Marketplaces and platforms. Sellers and buyers who already use PayPal and value its protection programs.
• Freelancers and service businesses. Sending hosted invoices with payment links through PayPal Invoicing.
• Complementary express checkout. Adding PayPal alongside cards (and often Stripe) to capture shoppers who prefer the PayPal wallet, Pay Later, or Venmo.

For competitive research and lead generation, detecting PayPal on a site indicates a merchant prioritizing consumer trust and broad acceptance, and it often appears alongside other processors, which pairs well with broader technology profiling.

Frequently Asked Questions

Is PayPal a payment processor or a wallet?

PayPal is effectively both. It processes payments by moving money between the buyer's funding source and the merchant, and it operates a consumer wallet that hundreds of millions of people use to pay across merchants without re-entering card details. For a merchant, this dual role is the point: PayPal brings its own trusted, logged-in user base to the checkout while also handling the underlying transaction.

How can I tell if a website uses PayPal?

Look for a script loading https://www.paypal.com/sdk/js, assets served from paypalobjects.com, and the global paypal object in the DevTools Console. The PayPal buttons render inside an iframe on PayPal's domain, clicking the button opens a paypal.com flow, and the site sets PayPal cookies such as ts_c. Wappalyzer and BuiltWith also flag PayPal reliably.

Why do so many stores offer PayPal alongside cards?

Because PayPal addresses a different part of the buyer's decision than a raw card field. Many shoppers trust the PayPal brand and its buyer protection, and they can pay with an existing account in a few clicks without typing card details. Offering PayPal alongside direct card payments (often via Stripe) captures both the shoppers who prefer the wallet and those who would rather pay by card, which can improve overall conversion.

Does PayPal give merchants control over the checkout design?

Less than a fully embedded custom checkout. PayPal's Smart Payment Buttons offer documented styling options, but the approval step runs on PayPal-hosted pages or an overlay, and the buttons themselves render in a PayPal iframe. This hosted approach simplifies security and compliance for the merchant but limits how deeply the experience can be customized compared with building a bespoke card form on a developer-first processor.

What are IPN and webhooks in PayPal?

Instant Payment Notification (IPN) and webhooks are PayPal's server-to-server notifications that inform a merchant's backend about events such as completed payments, refunds, and disputes. They matter because parts of the flow are asynchronous and happen on PayPal's side: by listening for these notifications, a merchant's system can reliably finalize orders, send confirmations, and update records based on PayPal's authoritative event rather than relying solely on the buyer's browser returning to the site.

Want to identify the payment processor, e-commerce platform, and marketing stack behind any site instantly? Try StackOptic at https://stackoptic.com.