Standard or Custom: which plan you actually need

Stripe publishes two tiers. Most companies start on Standard. A few graduate to Custom.

Standard is pay-as-you-go. Every published rate, no commitment. If you process under $80K per month, or use only one or two Stripe products, stay here.

Custom (Enterprise) covers volume discounts, multi-product discounts, and country-specific rates. No public minimum.

Start the Custom conversation when:

• Your card volume crosses $80K per month

• Your cross-border mix makes the 1.5% + 1% stack hurt margin

• You run Billing, Tax, and Connect together

Get Stripe to quote you line by line, including dispute-rate assumptions. Headline discounts can hide fine print.

Stripe pricing changes when you cross a border

Stripe charges US merchants the highest domestic card rate of any developed market it serves.

US merchants pay roughly twice the UK and EU rate on domestic cards. EU and UK merchants pay 2% on currency conversion, not 1%. UK-to-EU and UK-to-US cards sit between the domestic and non-EEA rates shown above. India has the widest domestic-to-international spread.

If you run US-incorporated SaaS selling mostly to EU customers, you are stuck on US-issuer-versus-international math. Your real cost is 2.9% + 1.5% + 1% + $0.30.

Some teams fix this by incorporating a subsidiary in the customer region. Talk to finance before you try it.

What Stripe customers actually say in 2026

Stripe's reviews split hard. Developer and SaaS reviewers rate it 4.0 to 5.0. Merchants who hit the risk engine rate it 1.8.

Both groups are telling the truth.

What positive reviews praise:

• API and docs (Capterra Ease of Use 4.5/5)

• Fast onboarding

• Flat published pricing

What negative reviews flag:

• Account freezes and 90-day fund holds when the risk engine triggers

• Slow, templated support

• Fees that compound on small tickets or heavy usage billing

One Capterra reviewer (Ashish T, April 14, 2026) put it plainly: "The risk management and compliance process can result in sudden account closures and prolonged fund holds."

Source

Stripe works if your business lives on the developer-experience side. It struggles on the compliance or usage-billing side.

When Stripe fits, and when it doesn't

Stripe fits you if

• You run US-first SaaS or e-commerce with 2 or 3 simple pricing plans, seat-based or fixed-price subscriptions, and card volume under $500K per month.

• You run a marketplace on Stripe Connect. Standard costs the platform nothing.

Stripe stretches you if

• You close enterprise deals with ramped pricing, for example "$1,000 for 3 months, $1,500 for 6 months, $2,000 after." Stripe does not model ramped contracts natively, so you track the schedule manually or create multiple plans.

• You negotiate quotes, renewals, and custom terms with mid-market customers. Stripe has no native quote system, so deal terms sit in Notion or PDFs until the subscription gets rebuilt.

• You sell internationally. The 1.5% + 1% stack compresses margin on every cross-border charge.

• You sell hybrid plans with a base fee plus usage plus seats plus credits.

Stripe starts to run out of room if

• You sell AI or token-metered products. The 1,000-events-per-second meter cap and 20-line-item subscription limit hit at scale. 

• You need parent-child account billing with shared credits across a customer's teams. Stripe treats each subscription as standalone.

• You want to charge differently for GPT-4o versus GPT-4 Turbo inside one event stream. Stripe asks you to create separate schemas for each variant.

• You operate in a policy-gray or high-dispute vertical. Account reviews can pause payouts until Stripe's risk team completes its checks.

Where Stripe Billing runs out of road, and how Flexprice slots in

Stripe built Billing for seat-based SaaS. It does that well.

It starts to strain the moment your pricing looks like an AI or enterprise deal. These are the areas where Stripe Billing is less flexible today, based on Flexprice's direct feature-by-feature comparison with Stripe:

• Ramped contracts. Stripe does not model deal timelines like "$1,000 for 3 months, $1,500 for 6 months, $2,000 after." You track the schedule manually or stand up multiple plans.

• Quotes and renewals. No built-in quote system. Terms sit in Notion or PDFs until the subscription gets rebuilt.

• Committed usage and credit pooling. No native support for volume commitments like "1 million API calls a month" or usage pooled across a customer's teams.

• Parent-child account billing. Stripe treats each subscription as standalone. No hierarchy. No shared credits or usage across a single organization.

• Granular usage filtering. You cannot price the same event stream differently by metadata. Charging separately for GPT-4o and GPT-4 Turbo means creating separate schemas.

• Feature entitlements. No native way to assign per-plan limits like "10 credits, 50 video minutes, 30 seconds of generative output."

• Recurring and rollover credits. Stripe supports one-time and promotional credits. Monthly grants, rollover caps, auto top-ups, and wallet thresholds require custom code.

• Custom credit values per feature. You cannot price a GPU-heavy action at more credits than a cheap one. Margin protection moves into application code.

• Contract amendments. Stripe shows the latest subscription config only. Historical versioning for upgrades, downgrades, and renegotiations lives in spreadsheets.

• Mixed billing intervals in one subscription. All products share one currency and one billing interval. No annual base plus monthly overage in a single subscription.

• Arbitrary aggregations. Stripe supports sum, count, and last. Count-unique, average, max, and weighted sum are not native.

• Throughput above 1,000 meter events per second per Stripe account.

• Gateway-agnostic billing. Stripe Billing runs on Stripe Payments only.

That list is why OpenAI, Anthropic, NVIDIA, and Databricks chose Metronome over Stripe Billing. Stripe paid $1 billion in January 2026 to catch up.

How Flexprice slots in

Flexprice is enterprise-grade monetization infrastructure built for AI-native companies. You run it alongside Stripe Payments, not instead of. Flexprice covers what Stripe Billing does not:

• Ramped contracts with auto-updating price timelines

• Built-in quotes, renewals, and negotiated pricing workflows

• Committed usage, pooled credits across teams, and parent-child account billing

• Granular filtering inside one event stream, so model: gpt-4o and model: gpt-4-turbo get priced differently without new schemas

• Feature entitlements with usage tracking and reset logic per plan

• Recurring and rollover credits with caps, expiration rules, auto top-ups, and wallet thresholds

• Custom credit values per feature to protect margins as backend costs shift

• Full contract history with versioning for audits and revenue forecasting

• Event-driven usage at scale with the aggregations Stripe does not support (count-unique, average, max, weighted sum)

• Gateway-agnostic setup, so you are not locked into Stripe Payments if you add other gateways later

• Self-hosting, so there is no revenue cut on your billing data

Stripe is good at payments. Flexprice handles everything pricing-related that happens after the card charges, which got harder the day AI pricing stopped looking like a seat.

If Stripe Billing fits your team, stay on Stripe Billing. If not, you know where to look next.

Read the Flexprice vs Chargebee vs Stripe comparison or star Flexprice on GitHub.

Wrapping up

Stripe is still the simplest developer-friendly payment stack you can plug in this afternoon. That counts for something.

What changed in 2026:

• Billing moved to a flat 0.7%

• The Metronome acquisition reshaped how Stripe sells to AI companies

• UK regulators started forcing 90-day closure notices

What did not change: 2.9% + $0.30 is your floor, not your ceiling. Once Billing, Connect, Tax, Radar, international, and disputes stack, your real rate sits 1 to 2 full points above the headline.

Model your stack before you commit.

If Stripe fits, ship. If not, you know where to look next.