Stripe

What Is Stripe?

Stripe is a developer-first payments platform that provides the APIs and infrastructure businesses use to accept payments and run financial operations online. The short answer to the most common question is that Stripe is one of the most widely used online payment processors in the world, particularly dominant among software companies, marketplaces, and modern e-commerce stores, and it is known above all for the quality of its developer experience.

Stripe was founded in 2010 by brothers Patrick and John Collison and has grown into payment infrastructure for millions of businesses, from early-stage startups to large enterprises. The company has publicly reported processing well over a trillion dollars in total payment volume in a single year, a figure cited in its own annual updates, which underscores the scale at which Stripe operates. Technology-detection surveys from sources such as BuiltWith consistently rank Stripe among the most-detected payment technologies across the web, with especially strong adoption among SaaS products and developer-built checkouts.

Rather than being a single checkout button, Stripe is a broad suite: core payment processing, subscription billing, marketplace payouts, tax calculation, fraud prevention, and more, all exposed through clean, well-documented APIs. That API-first approach, combined with test modes and client libraries for every major language, is why Stripe is the default choice for teams that build their own payment flows.

How Stripe Works

Stripe operates as a layer between a merchant's website or app and the card networks and banks that move money. The merchant integrates Stripe's APIs, and Stripe handles the complex, regulated work of charging cards, managing payment methods, and settling funds.

The most important architectural principle is that sensitive card data is tokenized on the client and sent directly to Stripe rather than touching the merchant's own server. Modern integrations load Stripe.js (served from js.stripe.com/v3) in the browser, which renders Stripe Elements, secure input fields hosted inside iframes served from Stripe's domain. Because the card number, expiry, and CVC are entered into Stripe-controlled iframes, the raw card details never pass through the merchant's page or backend, which dramatically reduces the merchant's PCI compliance burden. The browser exchanges those details for a token or a PaymentMethod, and the merchant's server then confirms the charge using a secret API key.

A typical payment lifecycle looks like this. The merchant's server creates a PaymentIntent through Stripe's API, representing the intended charge and its amount. The browser loads Stripe.js, mounts Elements (the iframed card fields), and collects payment details securely. When the shopper submits, Stripe.js confirms the PaymentIntent, handling any required authentication such as 3D Secure (Strong Customer Authentication in Europe) with an interstitial challenge. Stripe then communicates with the card networks and the issuing bank, returns a success or failure, and notifies the merchant's server asynchronously through webhooks, which are HTTP callbacks that fire on events like a successful payment or a dispute. This webhook-driven model lets the merchant reliably trigger order fulfillment, send receipts, and update records even if the customer closes the browser.

Several supporting products extend this core. Stripe Billing manages recurring subscriptions and usage-based pricing. Stripe Connect handles multi-party payments for marketplaces and platforms, splitting funds and managing payouts to sellers. Stripe Tax calculates and collects sales tax, VAT, and GST. Stripe Radar applies machine-learning fraud detection trained on data across Stripe's network. From a detection standpoint, the recurring theme is that Stripe runs significant logic client-side through Stripe.js and Elements, and it sets cookies (notably __stripe_mid and __stripe_sid) to support fraud signals and session continuity, while also sending telemetry beacons to Stripe-owned hosts such as m.stripe.com and r.stripe.com.

How to Tell if a Website Uses Stripe

Stripe leaves clear fingerprints in scripts, iframes, network beacons, cookies, and the DOM. Here are the signals to look for and the tools that surface them.

Signals in the page and network

• Stripe.js script. The strongest signal is a <script> loading https://js.stripe.com/v3/ (or older /v2/). Its presence almost always indicates a Stripe integration.
• The Stripe() global. Stripe.js exposes a global Stripe constructor. In the DevTools Console, typing Stripe or window.Stripe returns the function when Stripe is loaded.
• Stripe Elements iframes. Secure card fields render inside iframes whose src points to Stripe's domain (for example js.stripe.com). Inspecting the checkout's card inputs in the Elements panel reveals these nested iframes.
• Telemetry beacons. Watch the Network tab for requests to m.stripe.com (metrics) and r.stripe.com (reporting/fraud signals). These hosts are Stripe-owned and characteristic of an active integration.
• Cookies. Look for __stripe_mid (a longer-lived machine identifier) and __stripe_sid (a session identifier) in the Application/Storage tab. These are set by Stripe.js.
• Checkout and payment links. Hosted flows redirect to checkout.stripe.com, and Payment Links use the same hosted checkout, a definitive Stripe signal.

Tools to confirm it

Tool	What you do	What it reveals
View Source	Open the page source in your browser	A <script src="https://js.stripe.com/v3/"> tag
Browser DevTools (Console)	Type Stripe or window.Stripe	The Stripe() constructor confirms Stripe.js is loaded
Browser DevTools (Network)	Reach the checkout and watch requests	Beacons to m.stripe.com and r.stripe.com, Elements iframe loads
Browser DevTools (Application)	Inspect cookies	__stripe_mid and __stripe_sid cookies
curl -I	Run curl -I https://example.com	Header hints, though most Stripe signals are client-side and may not appear here
Wappalyzer / BuiltWith	Run the extension or look up the domain	Flags Stripe in the payment-processor category

Because Stripe is loaded in the browser, the most reliable detection happens with DevTools rather than curl. 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

Stripe spans the full lifecycle of online payments and financial operations.

• Payments API. Accept cards, digital wallets (Apple Pay, Google Pay), bank debits, and many local payment methods through PaymentIntents and Elements.
• Stripe Checkout and Payment Links. Prebuilt, Stripe-hosted checkout pages and shareable payment links that require minimal code.
• Stripe Billing. Subscriptions, metered/usage-based billing, invoicing, and proration logic.
• Stripe Connect. Multi-party payments, fund splits, and payouts for marketplaces and platforms.
• Stripe Radar. Machine-learning fraud detection and customizable risk rules.
• Stripe Tax. Automated sales tax, VAT, and GST calculation and collection.
• Strong developer tooling. Test mode with simulated cards, client libraries for major languages, interactive docs, and webhook testing.
• Dashboard. Real-time payment monitoring, customer management, dispute handling, and financial reporting.

A few capabilities stand out. Elements is the secure, iframe-based UI toolkit that keeps card data off the merchant's servers while allowing extensive styling. Webhooks are central to reliability, letting servers react to asynchronous events independent of the customer's browser. And test mode with clearly separated test and live API keys lets developers build and validate complete payment flows without moving real money, which is a major reason Stripe is so popular with engineering teams.

Pros and Cons

Stripe's strengths and trade-offs both stem from its API-first, developer-oriented design.

Pros

• Best-in-class developer experience with excellent documentation and SDKs.
• Broad product suite covering payments, billing, marketplaces, tax, and fraud.
• Secure, PCI-reducing Elements that keep card data off your servers.
• Wide support for international payment methods and currencies.
• Strong fraud prevention through Radar's network-trained models.
• Clear test mode that mirrors production for safe development.

Cons

• Building custom flows assumes some development capability; it is less turnkey than a simple button for non-technical users.
• Standard pricing is per-transaction, which can be costlier than some alternatives at very high volume without negotiation.
• Advanced features and disputes/chargebacks require operational attention.
• Account reviews and reserves can occasionally affect higher-risk businesses.
• Heavy reliance on client-side JavaScript means integrations must handle script-loading and SCA flows carefully.

Stripe vs Alternatives

Stripe competes with other payment processors and checkout providers. The right choice depends on how much you want to build versus buy, your technical resources, and your customers' trust expectations.

Provider	Primary model	Strength	Best for
Stripe	Developer-first APIs + hosted checkout	Developer experience, breadth of products	SaaS, marketplaces, custom checkouts
PayPal	Hosted buttons + consumer wallet	Consumer trust and recognition	Stores wanting a familiar buy button
Square	Integrated POS + online payments	Unified online/offline commerce	Retail and hospitality with physical and online sales
Adyen	Enterprise unified payments	Global acquiring at enterprise scale	Large international enterprises
Braintree (PayPal)	Developer-oriented gateway	PayPal/Venmo plus cards via one API	Teams wanting cards and PayPal together

If you want to compare against a consumer-trust-focused option, see our profile of PayPal, which covers the trade-offs in depth.

In short: choose Stripe when you are building a custom checkout or product and value developer experience and breadth; choose PayPal when consumer trust at the buy button is paramount; choose Square when you blend physical and online sales; and choose an enterprise processor like Adyen when you need global acquiring at massive scale. The most instructive comparison is Stripe versus PayPal, because many stores offer both. Stripe shines as the developer's payment engine, owning the card flow and back-office logic, while PayPal shines as a recognizable wallet that can lift conversion among shoppers who prefer paying with their PayPal balance. Offering both is common precisely because they serve different parts of the funnel.

Use Cases

Stripe fits a wide and recognizable set of scenarios.

• SaaS and subscriptions. Recurring billing, trials, proration, and usage-based pricing through Stripe Billing.
• Marketplaces and platforms. Splitting payments and paying out sellers via Stripe Connect.
• Custom e-commerce checkouts. Stores that build bespoke payment flows with Elements and PaymentIntents.
• Global selling. Businesses needing many local payment methods and currencies.
• Developer-built products. Apps that embed payments directly using Stripe's APIs and webhooks.

For competitive research and lead generation, detecting Stripe on a site signals a modern, often developer-led stack and a business comfortable building custom flows, which pairs well with broader technology profiling.

Frequently Asked Questions

Is Stripe a payment gateway or a payment processor?

Stripe functions as both in practical terms. It provides the gateway that securely captures and transmits payment details and the processing relationships with card networks and banks that move the money, plus the surrounding tools for billing, fraud, and reporting. For a merchant, the distinction is mostly academic: Stripe is the single provider that takes a customer's card and settles funds to the business.

How can I tell if a website uses Stripe?

Look for a script loading https://js.stripe.com/v3/, check the DevTools Console for the Stripe global, and inspect the checkout for Stripe Elements iframes served from Stripe's domain. In the Network tab, watch for beacons to m.stripe.com and r.stripe.com, and in the Application tab look for __stripe_mid and __stripe_sid cookies. Wappalyzer and BuiltWith also flag Stripe reliably.

Does using Stripe make a site PCI compliant automatically?

Using Stripe Elements or Stripe Checkout greatly reduces a merchant's PCI scope because card data is entered into Stripe-hosted iframes and never touches the merchant's server. This typically qualifies the merchant for the simplest PCI compliance path. However, PCI compliance is still the merchant's responsibility, and self-assessment requirements vary by integration; merchants should follow Stripe's guidance and complete the appropriate questionnaire.

How is Stripe different from PayPal?

Stripe is built for developers to construct custom payment flows and back-office logic, owning the card-entry experience through Elements and exposing deep APIs. PayPal is best known as a consumer wallet and a recognizable buy button that can boost trust and conversion. Many stores offer both: Stripe as the underlying card engine and PayPal as an additional, familiar checkout option for shoppers who prefer it.

What are Stripe webhooks and why do they matter?

Webhooks are HTTP callbacks Stripe sends to a merchant's server when events occur, such as a successful payment, a failed charge, a refund, or a dispute. They matter because payments are asynchronous: a customer might close the browser before the merchant's page confirms success. By listening to webhooks, a server can reliably fulfill orders, send receipts, and update records based on the authoritative event from Stripe rather than on the browser alone.

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