Stripe's pricing page says 0.7% on top of payment processing for subscriptions, and most founders take that number at face value when they're sketching out a budget. 

The bill you actually see six months in tells a different story, because Tax, Invoicing, fraud screening, disputes, and international card surcharges all stack on top in ways the homepage never really spells out.

The question isn't whether Stripe is good. The question is whether what you actually end up paying matches the shape of your business, especially if you're running an AI product or anything usage-heavy where Stripe's primitives start running out fast.

Every fee in this post comes from Stripe's pricing pages, and every limit comes from Stripe's own docs. By the end, you'll know whether Stripe is still your best call in 2026, or whether one of the alternatives now fits you better.

What people mean by Stripe subscription management

Source

Half the founders evaluating Stripe blur three different things together, so let's separate them before you spend a dollar.

Stripe Billing is the paid product that runs your subscriptions. It covers recurring charges, usage metering, dunning, the customer portal, and quotes. A custom domain on your customer portal costs an extra $10 a month per the live Billing pricing page.

Stripe Subscriptions is the older API name. Stripe migrated existing Subscriptions users into the more expensive Billing product back in 2020, which kicked off a Hacker News thread that founders still link to.

Stripe Payments is the underlying card processor at 2.9% plus 30 cents on US domestic cards. You cannot use Billing without it. Payments and Billing show up as two separate fees on your statement.

One thing you should know before you read the cost section. In February 2026, Stripe acquired Metronome, the usage-billing platform that OpenAI and Anthropic were already running on. The Stripe Billing pricing page now redirects multi-dimensional usage rates and negotiated contracts to "Contact sales," which is Metronome territory. 

That move tells you something about whether native Stripe Billing was ever built for the AI shape.

What you actually pay

Most evaluation pages stop at "2.9% plus 30 cents" and leave you to figure out the rest. Real subscription businesses pay more than that, and you should model the full stack before you sign.

Stripe Billing's live pricing page shows one tier in 2026, called Pay as you go, at 0.7% of Billing volume 

Source
Larger volume customers route to "Contact sales" above the 0.7% rate.

Underneath that, Stripe Payments charges 2.9% plus 30 cents on each successful US domestic transaction. International cards add 1.5%. Currency conversion adds another 1%. Manually entered cards add 0.5%. 

The layers most teams forget to model

Once you start adding the products most subscription businesses actually need, the cost stack starts climbing in ways the homepage never makes obvious.

• Stripe Tax costs 0.5% per transaction where you are registered to collect taxes. The API integration version costs $0.50 per transaction with 10 calculation calls included.

• Stripe Invoicing comes in two tiers. Starter is 0.4% per paid invoice, and Plus (which adds quotes) is 0.5% per paid invoice.

• Revenue Recognition runs 0.25% of volume, dropping to 0.2% once you're billing more than $100,000 a month.

• Disputes carry a $15 charge per dispute received, and that fee is non-refundable. If you fight a dispute manually, Stripe applies an additional $15 counter-fee, which you only get back if you win. Smart Disputes (Stripe's AI auto-evidence product) charges 30% of the disputed amount if you win, and nothing if you lose.

• Radar for Fraud Teams costs $0.02 per screened transaction on standard pricing. Adaptive Acceptance, the optional acceptance booster, adds 1% on top of accepted volume.

What you actually get for that 0.7%

The cost story is real, and the value story is real too. Here is what your Billing surcharge actually pays for:

• Smart Retries, Stripe's machine-learning dunning engine, recovers 56% of failed recurring payments on average, and the AI-powered version recovers 9% more revenue than fixed-schedule retries.

• The Customer Portal saves you from building self-serve account management yourself. Your customers update cards, cancel, switch plans, and view invoices on a Stripe-hosted page. The portal is included; only the custom domain ($10 a month) costs extra

• Multi-phase subscription schedules let you set up trial-to-discount-to-renewal flows of up to 10 phases per subscription. If your contract pattern fits in 10 phases, this works; if it does not, the next section explains why.

• Quotes now come bundled into the Pay as you go tier, so you can send a customer an estimate before turning it into a subscription.

• Stripe Meters includes 100 million usage events a month at the 0.7% price. For most SaaS shapes, that headroom is plenty; for a high-throughput AI workload, it is not. 

• Recovery automations and invoice auto-reconciliation come bundled too, with three configurable retry and state automations plus auto-reconciliation for ACH and wire payments (helpful for B2B finance teams). 

Where the 0.7% stops being worth it

The cost is one-half of the trade; the other half is what Stripe will actually let you build. For certain shapes (especially AI products and enterprise-contract heavy ones), the limits start hurting before the fee does.

The hard caps Stripe publishes in its own docs

Every limit below comes straight from Stripe's API and rate-limit documentation:

• Live mode API limit: 100 operations per second globally, with a 25 requests per second default per endpoint.

• Subscriptions API: 10 new invoices per subscription per minute, and 200 quantity updates per subscription per hour.

• Subscription line items: capped at 20 per subscription.

• Subscription schedule phases: capped at 10 current or future phases.

• Meter events: the standard endpoint takes 1,000 events per second, and concurrency is limited to one call per customer per meter. If you need more throughput, you switch to Meter Event Streams (10,000 per second), and anything beyond that requires a sales conversation.

Source

Why the 20-line-item cap hits AI products first

If you sell a multi-meter AI product, you almost certainly bill on more than 20 dimensions: input tokens, output tokens, image generations, function calls, vector operations, storage, embeddings, fine-tune storage, tool calls, and so on. 

Stripe gives you 20 slots per subscription, and once you hit that ceiling, you have to split a single customer across multiple subscriptions, which splits your invoices, complicates your data model, and pushes the problem into your ops team. 

The community workaround is documented in the Hacker News post:

Source

The primitives that aren't in Stripe Billing

This list reads from Stripe's own documentation gaps, not a competitor pitch:

• Ramped contracts get partial support through 10-phase schedules. If your enterprise deal looks like "$1,000 a month for the first 3 months, then $1,500 for 6 months, then $2,000 thereafter," you can model it. Anything more nuanced, or anything with mid-term changes, pushes you off native primitives.

• Quote-to-renewal-to-amendment flow is not native. You can send quotes, but you cannot manage the full lifecycle from quote through renewal through mid-cycle amendment with version history, which is exactly what most enterprise sales motions need.

• Committed usage with true-up gets partial support through credit grants, which are still in preview per stripe.com/billing/pricing. If a customer commits to 1 million API calls a month and burns through 1.2 million, you wire the overage logic yourself.

• Parent-child customer hierarchies are not supported. A holding company with three subsidiaries that each have their own teams cannot share usage credits across the parent. You either create separate accounts and lose unified reporting, or you build the hierarchy yourself in your backend.

• Granular usage filtering by dimension is partial. If you want to charge differently for GPT-4 input tokens versus GPT-4 Turbo input tokens versus image generations, you have to send separate event streams per variant, because Stripe does not filter on metadata inside a single event stream.

• Rollover credits and custom-value credits are not supported natively. Stripe handles one-time and promotional credits well, but recurring grants with rollover caps and custom expiration logic need workarounds in your code.

• Mid-term amendments with revision history are manual. When a customer renegotiates four months into a contract, Stripe shows you the current state, not the version history, and your finance team ends up rebuilding amendment trails in spreadsheets.

None of these gaps breaks Stripe for a card-charging, plan-based SaaS. They broke Stripe for the AI, agentic, and enterprise-contract shapes, which is the reason behind Stripe quietly outsourcing to Metronome in February.