Stripe

Overview

Stripe is a financial infrastructure platform for accepting payments, running subscriptions, embedding marketplace payouts, and automating tax and revenue workflows. Primary job: give software teams a single API and dashboard to charge cards, wallets, and local payment methods worldwide—without becoming a bank or building PCI infrastructure from scratch.

Company site: stripe.com. Pricing: stripe.com/pricing. Docs: docs.stripe.com. Status: status.stripe.com. GitHub: github.com/stripe.

Stripe reports processing about US$1.9 trillion in payments volume in 2025, support for 135+ currencies and payment methods, 200M+ active subscriptions on Billing, and historical service uptime around 99.999% (company homepage metrics). BFCM 2025 materials cite more than US$40bn processed over the Black Friday–Cyber Monday window with high reported uptime. Customers span startups (Cursor, Linear, Supabase, Lovable) through large commerce and platforms (Amazon, Shopify, Hertz, Instacart, URBN).

The product surface is deliberately modular: Payments (API, Checkout, Elements, Payment Links, Link), Billing (subscriptions + meters; advanced usage via Metronome partnership), Connect (platforms/marketplaces), Terminal (in-person), Radar (fraud), Tax, Invoicing, Issuing, Treasury, Identity, Sigma, Data Pipeline, Revenue Recognition, Atlas (US company formation), Capital, Climate, and newer agentic-commerce hooks (e.g. Instant Checkout / ACP messaging with AI platforms).

Key features

• Payments API & PaymentIntents — Core charge/capture model with SCA/3DS, saved payment methods, partial capture, and multi-method Payment Methods API. Industry-standard webhook events for lifecycle automation.
• Checkout — Hosted, conversion-oriented payment page with branding, subscriptions, tax hooks, and custom domain option (paid). Minimizes PCI scope for many merchants.
• Elements — Embeddable UI components for card fields, Payment Element, Address Element, etc., so you keep your site layout while Stripe tokenizes sensitive data.
• Payment Links — No-code URLs for products/subscriptions; creatable in Dashboard or via API for campaigns and sales ops.
• Link — Stripe’s accelerated checkout / wallet-like reuse of buyer details across participating merchants.
• Billing — Subscriptions, trials, coupons, proration, customer portal, Smart Retries and revenue recovery tooling. Usage-based path via Meters API (high included event volume) and deeper metering/analytics via Metronome partnership for complex models.
• Connect — Onboard sellers/creators, route multiparty charges (direct, destination, separate charges & transfers), platform fees, tax forms (e.g. 1099 e-file line items on Connect pricing), and embedded onboarding components.
• Terminal — In-person readers and SDKs (M2-class mobile, WisePOS E, S700-class smart readers—hardware SKUs/pricing on Terminal product pages). Unified online + offline ledger under one account.
• Radar — Network-trained ML fraud scoring. Basic protection commonly included on standard payments pricing; Radar for Fraud Teams adds rules/lists/controls at a per-screened-transaction fee (US market often cited around +$0.02–$0.07 depending on plan—confirm live Radar pricing).
• Tax — Calculate/collect sales tax, VAT, GST across many countries and product tax codes; threshold monitoring; filings via partners (e.g. TaxJar path for US); works with Checkout/Billing/API and even non-Stripe processors via Tax API.
• Invoicing, Sigma, Data Pipeline, RevRec — AR invoices, SQL analytics on Stripe data, warehouse sync, and ASC 606 / IFRS 15-oriented revenue recognition automation (each metered separately).
• Atlas — One-time ~US$500 Delaware C-Corp/LLC formation package (includes government fees + first-year registered agent per Atlas pricing copy), equity docs, EIN workflow, and Stripe onboarding funnel.
• Issuing / Treasury / Identity — Card issuing programs, money-movement accounts for platforms, and KYC/document verification products for higher-trust flows.
• Security posture — PCI DSS Service Provider Level 1; SOC 1 / SOC 2 Type II (reports on request); public SOC 3 summary. Checkout/Elements/Terminal SDKs shrink merchant card-data scope; merchants still attest PCI annually for their integration surface.

Pricing

Stripe is primarily usage-based: no setup fee and no monthly platform fee on standard pricing. You pay per successful charge plus optional product add-ons. Numbers below are the widely published US standard rates (confirm your country dashboard—rates are local). High-volume or unique models can negotiate Custom pricing with sales.

Product / method (US standard)	Typical fee	Notes
Online cards / major wallets	2.9% + $0.30 per successful charge	Core default for domestic US cards
International cards	Base + 1.5%	Non-US issued cards
Currency conversion	+ ~1%	When conversion is required
Terminal (card-present)	2.7% + $0.05	In-person via Terminal
Manually keyed cards	3.4% + $0.30	Higher risk / MOTO-style entry
ACH Direct Debit	0.8% (cap $5)	Common large-ticket / B2B path
ACH Credit / Wire / Checks	~$1 / ~$8 / ~$5	Bank rails (confirm live schedule)
Billing (subscriptions)	0.7% of Billing volume	On top of payment processing; excludes one-off invoices per Billing pricing page
Invoicing	0.4% per paid invoice	Standalone invoicing product
Tax	Often cited ~0.5% (volume tiers)	Confirm Tax product pricing for your registration status
Disputes / chargebacks	~$15 per dispute (US common quote)	Plus loss of goods/funds; Smart Disputes may take a % of won amount
Instant Payouts	Often ~1% (min applies)	Standard bank payouts free in many regions
Atlas	$500 one-time	Incorporation package
Checkout custom domain	$10/mo	Support FAQ pricing

How costs stack for SaaS: A $50 monthly subscription might pay ~$1.75 processing (2.9%+$0.30) + ~$0.35 Billing (0.7%) ≈ ~$2.10 before Tax/Radar extras—about 4.2% effective. International buyers and FX can push that higher. Refunds generally do not return the original processing fee (Stripe keeps the fixed portion / network costs depending on method).

Connect economics: Platforms can use Stripe-set pricing (simpler; optional revenue share paths) or platform-controlled pricing (platform pays processing and marks up; Connect may add starting ~0.25% and payout/account fees—see Connect pricing). 1099 e-file has separate per-form fees on Connect tax reporting lines.

Limits & gotchas

• Account freezes & held payouts — The #1 community complaint on r/stripe, r/SaaS, and HN: sudden reserves, 30–180 day holds, or permanent restrictions after volume spikes, chargeback waves, high-risk verticals, or incomplete KYC. Support is often ticket-only; plan cash reserves and a secondary processor if revenue is life-critical.
• Restricted businesses — Stripe’s prohibited/restricted categories (crypto edge cases, adult, some financial services, certain marketplaces) can block onboarding or trigger mid-life reviews. Read the restricted businesses list before building on Stripe alone.
• Effective rate creep — International cards, FX, Billing, Tax, and disputes routinely push all-in cost into the mid-single digits or higher for global SaaS.
• Refund economics — Buyer gets money back; you usually keep paying original processing costs—painful for high-return merchandise.
• Chargebacks — Flat dispute fee + product loss + time. Smart Disputes AI evidence can win cases but may take a cut of won amounts (preview pricing). Radar reduces fraud; it does not eliminate friendly fraud.
• Volume pricing is sales-gated — Interchange-plus / custom rates require scale and negotiation. SMBs stay on blended rates; large firms dual-source Adyen, Worldpay, or direct acquiring.
• Connect complexity — Marketplace compliance (KYC on connected accounts, tax forms, negative balances, platform liability) is a product, not a checkbox. Budget engineering and ops.
• PCI is shared — Using Stripe does not auto-make you PCI-complete. SAQ choice depends on integration (Checkout vs raw card data). PCI DSS 4.x script monitoring still applies to payment pages.
• Vendor gravity — Billing objects, invoices, tax IDs, and Connect graph create real migration cost. Abstraction layers (payment service interface) are common HN advice.
• Support tiers — Free/email vs paid support plans. Enterprises buy TAM/professional services; bootstrappers often feel alone during freezes.

Community sentiment

Across r/stripe, r/SaaS, r/nextjs, and Hacker News, Stripe is the default developer payment stack—and the processor people fear for fund freezes.

Praise: documentation quality; weekend-to-production Checkout/Elements path; Billing for SaaS; Connect for marketplaces; Terminal for omnichannel; Radar defaults; reliability at BFCM-scale; Atlas funnel for foreign founders raising US VC; ecosystem of samples and official SDKs on GitHub.

Criticism: opaque risk reviews with limited human support; multi-month freezes after viral launches; blended fees expensive vs negotiated merchant accounts; stacked Billing/Tax percentages; dispute friction; arbitration-heavy terms narratives on HN; “never put 100% of cash flow on one PSP” advice repeated constantly.

Review sites: G2 seller aggregates often sit around ~4.4/5 across Stripe products; Capterra listings show thousands of reviews with strong marks for ease of integration and reliability, with cost predictability and account risk as recurring knocks. TrustRadius threads include both glowing DX stories and sharp warnings about holds and support. Comparison pieces in 2025–2026 commonly rank Stripe for SMB/dev UX, Adyen for enterprise unified global acquiring, PayPal for consumer trust/buyer base, Square for SMB in-person, and Paddle/Lemon Squeezy for merchant-of-record SaaS.

Who should use it

• SaaS and internet product teams that want Billing + Tax + global cards in one integration.
• Marketplaces and platforms ready to invest in Connect onboarding, KYC, and multiparty money movement.
• Omnichannel retail needing Terminal + online under one reconciliation story.
• Startups and foreign founders using Atlas + Stripe to open a US company and accept payments quickly.
• Developers who value first-class docs, webhooks, and multi-language SDKs over the lowest possible interchange rate on day one.

Who should pause or dual-source: high-chargeback verticals on the restricted list; businesses that cannot survive a multi-week payout hold; very high domestic volume ready for interchange-plus; sellers who only need PayPal buyer base; pure MoR preference (Paddle-class) to offload tax/compliance entirely.

Alternatives

• PayPal / Braintree — Broader consumer recognition; Braintree is the closer API peer. Different risk and fee profile; often paired with Stripe rather than pure replace.
• Square — Strong SMB POS + simple online; less “full financial OS,” often cheaper/simpler for local retail.
• Paddle — Merchant of record for software: handles tax/compliance/checkout; higher effective cut, less payment plumbing.
• Lemon Squeezy — MoR-style for indie/SaaS digital products; simpler than Connect+Tax DIY.
• Shopify Payments — Best when the storefront already is Shopify; Stripe-powered under the hood in many markets but ecosystem-locked.
• Adyen — Enterprise unified commerce, often better negotiated rates and global acquiring depth; heavier sales process than Stripe self-serve.
• Authorize.net / traditional merchant accounts — Lower unit cost at scale with more ops; weaker modern DX than Stripe.

Verdict

Stripe remains the default payments platform for software-led businesses because the API, Checkout/Elements, Billing, Connect, and Tax stack ship faster than piecing together a bank, tax engine, and fraud vendor. The public US card rate of 2.9% + $0.30, plus Billing at 0.7% and optional Tax/Radar, is transparent enough for startups and expensive enough that scaled companies negotiate custom rates or add a second processor.

Use Stripe when developer velocity and product breadth matter more than absolute interchange optimization. Treat freezes and reserves as a real operational risk: complete KYC early, document business model, set conservative refund/chargeback policies, keep operating cash outside a single payout balance, and design payment abstractions so you are not one Dashboard banner away from zero revenue. For pure digital goods MoR simplicity, look at Paddle/Lemon Squeezy; for enterprise multi-acquirer control, evaluate Adyen; for local POS-first SMB, evaluate Square—while keeping Stripe as the benchmark for documentation and modular fintech APIs.