Stripe: The Complete Picture

What Stripe does brilliantly, where its economics erode, and how to make the migration decision with clear eyes.

24 min read

Stripe at scale: where the company is in 2026

Before evaluating Stripe as a vendor for your platform, it’s worth understanding the scale and trajectory of the business you’re considering integrating with. Stripe is no longer the developer-tools startup of 2015; it is one of the largest financial infrastructure companies in the world.

Volume: Stripe processed $1.9 trillion in total volume in 2025, growing 34% year-over-year (versus 38% in 2024 — a modest deceleration). For comparison, Adyen processed approximately $1.6 trillion ex-Cash App in the same period, growing 20%. Stripe overtook Adyen on TPV by approximately $300 billion in 2025 and is growing materially faster.

Globalization: 57% of new 2025-cohort Stripe customers were based outside the United States. The new-customer cohort is growing roughly 50% faster than the 2024 cohort. Stripe is no longer primarily a US-centric platform; it is a globally distributed infrastructure layer.

Embedded finance products: Stripe Capital funding volume grew 45% in 2025. The Revenue Recognition Suite is on track to hit $1B in annual revenue run rate in 2026. Treasury, Issuing, and Atlas continue to expand. Each adjacent product compounds switching cost for platforms already using Stripe Connect.

Stripe’s product universe

Stripe is no longer just a payment processor. It has evolved into a financial infrastructure platform that touches nearly every aspect of online commerce and software monetisation. Understanding the full product map is essential — both for evaluating what you’re buying when you embed Stripe, and for understanding the switching costs you accumulate over time.

The product breadth is genuinely impressive — and genuinely sticky. A platform using Stripe Connect + Billing + Terminal + Treasury has built four separate integrations, each with its own API surface, migration complexity, and team familiarity advantage. This is not an accident; it is Stripe’s deliberate platform strategy.

Stripe Connect deep dive: the three account types

The account-type decision is one of the most consequential technical choices a platform makes when implementing Stripe Connect. It determines the economics, the liability model, the user experience, and the long-term switching cost. Most platforms choose Express because it is the path of least resistance — but the choice deserves more deliberate analysis.

Standard accounts — the lightest touch

Standard accounts are the simplest implementation: the connected account has its own full Stripe account, pays Stripe directly, and Stripe handles all dispute liability. The platform earns via an application fee — a set amount or percentage that Stripe routes from the connected account’s payment to the platform’s balance.

The critical implication: the platform is not in the payment flow from a risk or liability perspective. This is attractive for loosely coupled marketplaces (crowdfunding, peer-to-peer) where the platform doesn’t want to bear responsibility for seller fraud. The downside: the platform has essentially no control over merchant pricing, onboarding quality, or payment experience. The seller sees Stripe, not the platform.

Express accounts — the middle path

Express accounts are the most commonly chosen model for vertical SaaS platforms implementing Connect for the first time. Stripe hosts the onboarding flow and provides a Stripe Express dashboard to connected accounts, but the platform has more configuration control than Standard.

The fee structure ($2/active user/month + 0.25% + $0.25 per payout) creates a per-merchant cost that compounds as the platform scales. At 1,000 active merchants paying $2/month each, that’s $24,000 annually in Connect fees before a single payout fee. At 10,000 merchants, the math becomes pointed.

Critically: the platform is now liable for chargeback losses on Express accounts. This is a substantive operational change that many platforms discover after the fact. Budget for reserves accordingly.

Custom accounts — full control, full responsibility

Custom accounts give the platform full UI/UX control — no Stripe branding, platform-controlled onboarding flows, and access to Stripe Embedded Components (launched 2023) to build a fully integrated payment experience within the platform’s existing product surfaces.

The fee structure is identical to Express ($2/active user/month + 0.25% + $0.25/payout), but the implementation complexity is approximately 4x higher. The platform controls every aspect of the merchant experience — and is entirely responsible for chargeback losses, KYC quality, and compliance attestation.

Stripe’s Embedded Components, launched in 2023, have materially reduced the frontend build effort for Custom accounts. Components for payment collection, payouts, account management, and reporting can be dropped into existing React applications, narrowing the gap between Express and Custom integration effort.

The economics of Stripe

Flat-rate pricing vs. interchange-plus

Stripe’s base model for card transactions in the US is 2.9% + $0.30 per successful transaction. This is a flat rate — meaning Stripe charges the same for a $50 debit card transaction at a convenience store as for a $5,000 Visa Signature Business card transaction, even though the underlying interchange costs are wildly different.

The economics of flat-rate pricing are straightforward: Stripe takes the blended interchange cost across all transactions (roughly 1.5–2.2% for most consumer credit card mixes), adds its margin, and charges everyone the same rate. Low-risk, low-interchange transactions (debit cards, consumer Visa/MC) subsidize high-interchange transactions (premium rewards cards, commercial cards). Platforms with a debit-heavy or B2B card mix are disproportionately overpaying.

An interchange-plus (IC+) provider like Rainforest, Finix, or Adyen charges the exact interchange rate for each transaction (passed through from the card networks), plus a fixed markup. Platforms with access to their interchange data can model exactly what they would pay on IC+ versus flat rate.

Illustrative figures. Actual savings depend on your card mix, average transaction size, and IC+ provider terms. The point: economics become material above $20–30M GMV and become hard to ignore above $50M GMV.

The application fee model — how platforms earn on Stripe

Platforms using Stripe Connect earn revenue via the application fee model: a per-transaction fee set by the platform that Stripe routes from the connected account’s payment to the platform’s balance. This gives the platform a simple mechanism to capture payment economics without setting up a full billing relationship with each merchant.

Example: A merchant processes $100. The platform sets an application fee of $0.50. Stripe deducts its fees (2.9% + $0.30 = $3.20), routes $0.50 to the platform’s Stripe balance, and the connected account receives $96.30. The platform’s revenue is the $0.50 application fee — regardless of Stripe’s actual interchange cost on that transaction.

The limitation: the platform earns a fixed fee it sets, but has no visibility into Stripe’s underlying cost structure. There is no “margin” in the traditional sense — just the spread between the application fee and zero (since the platform doesn’t pay Stripe’s processing fee; the connected account does). This model is simple but opaque, and it means the platform cannot optimise pricing based on interchange data it doesn’t have access to.

The $50M GMV inflection point

Charge Forward’s view, consistent with industry analysis: the economic argument for migrating away from Stripe’s flat-rate model becomes compelling around $20–30M GMV and urgent around $50M GMV. The specific numbers depend on card mix and average transaction size, but the directional analysis is consistent across scenarios.

At $10M GMV: The difference is ~$100–200K annually. Real money, but likely outweighed by integration switching costs.

At $50M GMV: The difference is potentially $500K–$1M+ in annual savings. Now it pays for itself in under 12 months against a migration investment.

At $100M GMV: The difference is $1M–$2M+ annually. This is a strategic imperative, not just an optimisation exercise.

Enterprise negotiation: custom rates at volume

Stripe does negotiate custom rates for enterprise platforms. The threshold at which Stripe will engage meaningfully varies — informally, platforms processing $20M+ GMV annually can typically get Stripe’s attention. The negotiation levers are: volume-based discounts on the processing rate (e.g., 2.5% instead of 2.9%); reduced or waived Connect fees for Express/Custom accounts; custom rate cards for specific payment method categories; dedicated account management and SLA commitments.

The catch: you cannot get Stripe’s interchange data, so you cannot verify whether the negotiated rate is still more expensive than IC+. You are still paying a blended rate; you just don’t know the blended cost.

Charge Forward Insight

A pattern we see consistently in advisory work: platforms that have been on Stripe for 2+ years almost never re-negotiate proactively. They accept whatever rate they signed at, watch GMV grow 5–10x, and are surprised to discover they have $300K–$700K of annual fees that could be reduced just by initiating a conversation. The single highest-ROI action a platform on Stripe at $20M+ GMV can take this quarter is to email their account manager (or request one) with their last 12 months of fee data and ask for a rate review. Most platforms recover material savings without leaving Stripe at all.

When Stripe is the right choice

This chapter’s analysis should not be read as an anti-Stripe argument. Stripe is the right choice in specific, well-defined circumstances — and choosing it in those circumstances is not a mistake.

1. You are early-stage (sub-$10M GMV)

For early-stage platforms, the priority is proving product-market fit and getting merchants processing payments as quickly as possible. Stripe Connect Express can be live in 1–3 weeks with minimal engineering investment, no minimum volume requirements, and institutional-grade infrastructure. The economics are less favourable than IC+, but at $1M GMV the annual difference is $15,000–$25,000 — not worth the integration overhead of a more complex vendor.

2. Developer experience is your competitive constraint

Stripe’s documentation, API design, developer tooling, and community support are genuinely superior to all alternatives. If your engineering team’s bottleneck is developer productivity — if you’re moving fast and payment infrastructure is not your core product — Stripe’s DX advantage is real and worth paying for. No other vendor comes close on the combination of API quality, documentation depth, and developer ecosystem.

3. You need global reach immediately

Stripe Connect is available in the US, Canada, UK, all EU/EEA countries, Australia, and several APAC markets. With 57% of Stripe’s 2025 new-customer cohort outside the US, the company is investing aggressively in global infrastructure. If your platform has international merchants from day one, Stripe is the most practical way to serve them. Adyen is technically superior for global acquiring, but its minimum invoice requirements and integration complexity make it inaccessible at early stage. For a pre-$50M platform with international merchants, Stripe + a plan to migrate later is a reasonable strategy.

4. You have a diverse Stripe product stack dependency

If your platform uses Stripe Billing for subscriptions, Stripe Terminal for in-person, and Stripe Treasury for embedded banking — not just Stripe Connect — the migration calculus changes dramatically. You are not evaluating a single integration switch; you are evaluating a fundamental re-architecture of your financial infrastructure. At that point, the economics must be very compelling to justify the migration risk.

5. Your platform is in a highly regulated vertical

Stripe’s compliance infrastructure, Radar fraud prevention, and institutional track record carry significant weight in highly regulated verticals (healthcare, financial services, government). The reputational safety of “we use Stripe” as an answer to a compliance question has real value in enterprise sales cycles. Alternative providers may not carry the same institutional credibility, even if their product is technically equivalent.

6. Speed to market trumps everything

For platforms with a specific market window — a conference launch, a partnership go-live, a competitive pressure deadline — Stripe’s speed advantage can be decisive. A 3-week Stripe integration versus a 3-month Finix integration is not just a cost difference; it can be a market timing advantage. Speed has real economic value that doesn’t show up in processing fee comparisons.

When to consider alternatives

The following signals are decision triggers — they don’t necessarily mean you should leave Stripe, but they mean you should run the analysis. If multiple signals apply simultaneously, the analysis should be prioritised.

Signal 1: You are paying more than IC+ + ~$0.15/transaction

Run a simple calculation: take your last month’s total Stripe fees (processing fees, not Connect fees), divide by total transaction count. If the per-transaction cost exceeds what you would pay on IC+ with a modest markup, you have an economic case to evaluate. At typical US card interchange rates (1.5–2.0% blended for consumer credit, 0.5–0.8% for debit), Stripe’s flat rate is often 50–100 basis points more expensive than IC+ for consumer businesses. For B2B platforms with commercial card mixes, the gap is smaller but Level 2/3 optimisation is available on IC+ platforms (Finix, Adyen) and not on Stripe — a meaningful savings opportunity.

Signal 2: You need interchange transparency

If you want to understand the actual cost of each transaction — the interchange rate, the network fee, your processing margin — Stripe will not give you that data. It is simply not available in the Stripe model. If interchange transparency matters for your pricing strategy, financial modelling, or investor reporting, you need an IC+ provider.

Signal 3: You are processing more than $50M GMV annually

At this volume range, the annual cost differential between Stripe flat rate and IC+ typically exceeds $500K. This is the threshold at which a migration investment (engineering costs, potential merchant re-onboarding) pays back within 12 months. Calculate your specific number — but directionally, $50M GMV is the tipping point.

Signal 4: You want to own the merchant relationship

On Stripe Connect Express and Standard, the merchant has a relationship with Stripe as well as with your platform. They see Stripe branding, they deal with Stripe support for payment issues, and Stripe has data about their transaction history. For platforms that want the merchant relationship fully owned — for upsell, retention, and strategic reasons — Custom accounts or a non-Stripe provider are better fits.

Signal 5: Card-present at scale

Stripe Terminal is a capable in-person payments product, but it is not best-in-class for platforms with large card-present deployments. Adyen’s 255,000+ terminals (with POS volume growing 59% YoY in H2 2025), Tilled’s Handpoint integration, and Payrix’s enterprise POS infrastructure offer more depth and lower per-terminal cost at scale. If card-present is a significant part of your GMV, run a specific card-present cost analysis before committing to Stripe Terminal.

Signal 6: Your commercial card mix makes Level 2/3 savings material

If your platform serves B2B merchants — professional services, healthcare, contractor services — a significant portion of transactions may involve commercial credit cards (Visa Business, Mastercard Corporate, Amex Corporate). Level 2/3 transaction data (providing additional purchase details like customer code, purchase order number, and item descriptions) qualifies these transactions for lower interchange rates. Stripe does not support Level 2/3 optimisation. Finix and Adyen do. The savings can be 30–60 basis points on qualifying transactions — material for B2B-heavy platforms.

⚠ On making the alternative case internally

One underappreciated challenge in pursuing a migration away from Stripe is making the internal case. Engineering teams have Stripe familiarity and resist re-integration. Finance teams see the switching cost as a capital expenditure with uncertain return. Leadership teams are comfortable with Stripe’s brand. The strongest internal argument is a precise economic analysis: “we pay $X to Stripe annually. On IC+ with [specific vendor], we would pay $Y. The annual savings of $Z pay back a migration investment of $W in N months.” The vaguer the numbers, the harder the sell. Charge Forward’s Payments Revenue Calculator runs this analysis on your specific volume and card mix.

The migration challenge

Moving away from Stripe is harder than it looks. This is not a scare tactic — it is a genuine operational reality that platforms repeatedly underestimate. Understanding the migration challenge is essential both for deciding whether to migrate and for designing a migration that minimises disruption.

Challenge 1: Token vault lock-in

This is the most underappreciated and most significant migration barrier. When a merchant’s customer saves a card on a Stripe-powered platform, Stripe generates a token tied to Stripe’s vault. That token cannot be transferred to another processor. It is, functionally, a Stripe-only credential.

The practical implication: if you migrate to a new processor and want to maintain saved payment methods for your merchants’ customers, you must re-collect card data from those customers. This means customer-facing friction — a “please re-enter your card details” message — which generates churn, abandoned payments, and customer service volume.

Mitigation options are limited but exist: Stripe Token Portability (Stripe does provide a token migration service for platforms meeting certain criteria — evaluate this option early in any migration planning); new-customer-first migration (migrate only new merchants and new customers to the new processor; existing merchants remain on Stripe until natural attrition refreshes the token vault over 12–24 months); parallel processing (run both processors simultaneously during a transition period — complex to implement but minimises customer-facing disruption).

Challenge 2: Integration depth

A platform using only Stripe Connect has a contained migration. A platform using Stripe Connect + Stripe Billing + Stripe Terminal + Stripe Treasury has four separate integrations to migrate, each requiring engineering resources, testing, and operational validation. The cost and risk of migration scales roughly linearly with the number of Stripe products in the stack.

Before scoping a migration, map every Stripe product your platform uses. Assign an engineering estimate to migrating each. Sum the total. Compare against the annual economic savings. If the payback period exceeds 18 months, reconsider the scope — perhaps migrate Payments first, defer Billing and Terminal.

Challenge 3: Team familiarity and documentation advantage

Stripe’s documentation is genuinely outstanding. Engineers who have worked with Stripe for years have institutional knowledge of its quirks, error codes, edge cases, and operational patterns. Transitioning to a new provider means rebuilding that knowledge base — a real but intangible cost. Budget for a learning curve in any engineering estimate.

Challenge 4: Merchant re-onboarding

For platforms using Stripe Connect Express or Custom, each connected account (merchant) has completed Stripe’s KYC/KYB onboarding process. Migrating to a new provider means re-onboarding each merchant through the new provider’s KYC process. This creates merchant friction and churn risk during re-onboarding; potential approval-rate differences between processors (some merchants approved by Stripe may be declined by the new provider, or vice versa); and engineering effort to build and maintain a parallel onboarding flow during the transition period. Vendors like Rainforest explicitly offer managed migration services — white-glove onboarding support designed to minimise merchant re-onboarding friction. This is a genuine differentiator when evaluating migration-friendly providers.

Practical migration approaches

Phased migration by merchant cohort. Migrate merchants from newest to oldest. New merchants onboard directly to the new provider. Existing merchants migrate on a scheduled cadence with dedicated communication and support.

Parallel processing. Run both processors simultaneously. New transactions and new merchants route to the new provider. Existing Stripe relationships maintain until natural expiry. Operationally complex but minimises disruption.

Product-by-product migration. Migrate payment acceptance first. Defer subscription billing, terminal, and treasury until the core payments migration is stable. Reduces risk surface at each step.

Greenfield migration. For platforms adding a new geographic market or a new product line, launch the new market or product on the new provider while maintaining existing operations on Stripe. The cleanest approach — applicable where a natural greenfield opportunity exists.

Charge Forward Insight

In our advisory work, the migration question is rarely “should we migrate?” — it is “what is the lowest-risk path to capturing the economic upside?” The platforms that execute migrations cleanly almost always use one of two approaches: phased-by-cohort (newest merchants first, with a 6–12-month tail) or product-by-product (Payments first, then Billing or Terminal in subsequent quarters). The platforms that struggle are those that attempt a full big-bang cutover. Our migration playbook for advisory clients explicitly forbids big-bang. The math is real, the engineering is tractable, and the migration risk is manageable — but only if you sequence it.

Stripe’s evolution

Stripe’s trajectory over the past five years has been consistent: layer financial services onto the core payments rails, expand into every adjacent use case, and increase the total revenue per platform. Understanding this trajectory helps anticipate where Stripe is going and what it means for platforms embedding Stripe today.

2023: Embedded Components and the Custom-account experience

Stripe launched Embedded Components in 2023 — a library of drop-in UI components for payment collection, payouts, account management, and reporting that can be integrated into existing React applications. This was a direct response to the primary objection to Stripe Connect Custom: “we don’t want to build the entire payment experience from scratch.” Embedded Components significantly reduced the gap between Express (managed experience) and Custom (full-control) in terms of implementation effort.

The strategic implication: Stripe is investing in making Custom accounts more accessible, which should drive more platforms toward the Custom path — and deeper integration lock-in.

Treasury: the banking-as-a-service expansion

Stripe Treasury, launched in 2020 and expanded significantly in subsequent years, enables platforms to offer their connected accounts FDIC-insured financial accounts, physical and virtual debit cards, and money movement. The strategic rationale: platforms that offer banking alongside payments create dramatically higher merchant stickiness. Treasury is backed by Stripe’s banking partners (Goldman Sachs, Evolve Bank & Trust, Fifth Third Bank). The competitive implication: platforms that implement Treasury are adding a category of switching cost — banking relationships — that is even harder to move than payment tokens.

Capital: merchant lending as a retention tool

Stripe Capital offers cash advances and loans to connected accounts based on their Stripe processing history. The merchant repays as a percentage of future sales. Stripe Capital funding volume grew 45% in 2025 (per Stripe’s 2025 annual letter). For platforms, this creates a powerful retention mechanic: a merchant who has borrowed from Stripe Capital and is actively repaying via Stripe will not migrate their payment processing without first addressing the lending relationship. The lending economics work because Stripe has real-time visibility into merchant payment volume and cash flow — giving it an underwriting advantage that traditional lenders cannot replicate.

Pricing evolution

Stripe’s published pricing has remained at 2.9% + $0.30 for US card transactions for years, but the negotiated pricing available to enterprise volumes has become more structured — Stripe now has a formal enterprise programme with dedicated account management. The key observation: published rate has not changed significantly in years, but the negotiated rate available to large platforms has moved, reflecting competitive pressure from IC+ providers.

Negotiating with Stripe

Most platforms on Stripe are paying more than they need to. Stripe does negotiate — but only for platforms that ask, and only for platforms above informal volume thresholds. Here is a practical playbook for the negotiation.

Who gets a custom rate

Informally, Stripe will engage on custom rates for platforms processing approximately $20M+ GMV annually (i.e., generating ~$500K+ in annual Stripe fees). Below that threshold, you are unlikely to get meaningful movement. Above $50M GMV, you have significant leverage.

The negotiation playbook

Step 1. Gather your data. Pull your last 12 months of Stripe fees, broken down by product (processing, Connect fees, dispute fees). Know your total Stripe spend to the dollar.

Step 2. Get competitive quotes. Run a genuine evaluation of 2–3 IC+ providers (Rainforest, Finix, Tilled are good choices for this exercise). Get specific pricing for your volume and card mix. This gives you a credible BATNA.

Step 3. Reach out to your Stripe account team — or if you don’t have one, request one through the Stripe sales page. Frame the conversation as: “we are evaluating our payment infrastructure options for the next 24 months and want to understand what Stripe’s enterprise offering looks like for our scale.”

Step 4. Share your processing data and request a custom rate card. Stripe will need your monthly GMV, transaction count, average ticket size, and geographic mix to prepare a proposal.

Step 5. Evaluate the offer against your competitive quotes. Remember that even a negotiated Stripe rate is still a blended rate — you cannot verify its competitiveness against IC+ without modelling your specific interchange mix.

Step 6. Use the competitive quotes as leverage. “Provider X is offering us IC+ with a $0.20/transaction markup. Your proposal needs to be competitive with that on a total-cost basis.”

What you can negotiate

• Processing rate reduction (e.g., 2.5%–2.7% instead of 2.9%) — most common lever
• Waived or reduced Connect fees for large connected account counts
• Reduced international card processing surcharges
• Dedicated account management and priority support SLAs
• Custom handling of specific payment method categories (ACH, SEPA, etc.)

What you cannot negotiate away

• Interchange transparency — Stripe will not give you underlying interchange data
• Token portability — unless you qualify for Stripe’s token migration programme
• The fundamental architecture of the application fee model

Charge Forward Insight

We have worked with platforms at every stage of the Stripe relationship — companies evaluating Stripe for the first time, companies deeply embedded in Stripe’s ecosystem negotiating better rates, and companies two years into a migration that is taking longer than expected. Our honest assessment: Stripe deserves its reputation. The developer experience is genuinely excellent, the documentation is outstanding, and the global coverage is unmatched at early stage. For a platform from $0 to $10M GMV, Stripe is the right choice in almost every case. The strategic mistake we see repeatedly is inertia past the inflection point. Platforms that are generating $50M+ in GMV and have not run a serious cost analysis in the past 12 months are almost certainly overpaying. Our typical recommendation: negotiate with Stripe at $20M GMV, model the migration at $30M, and make a go/no-go migration decision at $50M GMV. The decision depends on your card mix, engineering capacity, and product roadmap — but those are the thresholds where the analysis is worth doing in detail.

What’s Next

Chapter 5 — “Mastering Payment Economics” — provides the financial modelling framework you need to make the analysis in this chapter rigorous. It covers interchange economics, markup structures, effective rate optimization, and revenue modelling at various GMV tiers. The chapter is anchored by Charge Forward’s Payments Revenue Calculator — the same tool we use in advisory engagements to build the migration business case.

See the Benchmarks chapter for company-specific volume figures and the most recent take-rate data referenced throughout.

SOURCES & REFERENCES

Stripe, “2025 Annual Letter” (February 2026); UBS Global Research, Tim Chiodo, “Fast Take: Stripe Annual Letter — Stripe 2025 annual letter; $1.9tr of total volume” (February 24, 2026).

UBS Global Research, “Innovation in Payments & FinTech: Stripe Tour 2025” (October 2, 2025); “First Read: PayPal Holdings Inc — Stripe Reportedly Considering Acquisition” (February 25, 2026).

Stripe public documentation: Stripe Connect (Standard, Express, Custom), Stripe Billing, Stripe Terminal, Stripe Treasury, Stripe Capital, Stripe Radar, Stripe Atlas, Stripe Tax, Stripe Identity, Stripe Issuing, Stripe Sigma, Stripe Embedded Components.

Public Charge Forward tools referenced in this chapter: Vendor Database (includes Stripe-specific vendor analysis), Embedded Payments Maturity Framework, Payment Model Fit Navigator, Payments Revenue Calculator, Embedded Payments Fit Assessment. All available at chargeforward.io/tools.

By Jane Podbelskaya · Updated April 30, 2026