Stripe Billing pricing follows a pay-as-you-go model based on eligible billing volume, with monthly subscription plans available under annual contracts. The platform supports recurring subscriptions, automated invoicing, payment recovery, and usage-based billing. Payment processing, tax automation, revenue recognition, and advanced usage-based billing can introduce additional charges.
For SaaS, AI, and cloud infrastructure companies, total costs also depend on usage-event volume, enterprise contract requirements, integrations, and ongoing finance workflows. This guide breaks down Stripe's published US pricing and the factors that influence its total cost of ownership.
Key takeaways
- Stripe Billing charges 0.7% of eligible billing volume under its pay-as-you-go plan, with separate monthly subscription and custom pricing options
- Monthly plans range from $620 to $5,750 under annual contracts, with a 0.67% rate for additional billing volume beyond the included allowance
- Payment processing, Stripe Tax, and Revenue Recognition have separate fees that contribute to total billing costs
- Basic usage-based billing includes up to 100 million meter events monthly, while Metronome provides advanced usage-based pricing under a separate commercial structure
- Total cost of ownership depends on billing volume, payment methods, event ingestion, integrations, and the operational requirements of the pricing model
Understanding Stripe Billing's pricing model
What Stripe Billing provides
Stripe Billing manages recurring revenue through subscription creation, pricing configuration, invoicing, and payment collection.
Its core capabilities include:
- Subscription management: Fixed recurring fees, per-seat plans, and tiered subscription structures
- Usage-based billing: Metered charges based on recorded product activity
- Automated invoicing: Recurring invoice generation and payment collection
- Subscription schedules: Planned commercial changes across multiple subscription phases
- Proration: Billing adjustments when subscription terms change mid-cycle
- Customer portal: Self-service billing and payment method management
- Revenue recovery: Automated payment retries and reminders
Stripe Billing operates alongside Stripe Payments, Tax, Revenue Recognition, and Metronome. The configuration depends on whether a business uses recurring subscriptions, usage-based charges, or hybrid pricing.
Pay-as-you-go pricing
Stripe Billing's standard pay-as-you-go plan charges 0.7% of eligible Billing volume, without a recurring subscription fee.
Billing volume includes qualifying recurring billing transactions processed through Stripe or supported external payment arrangements. One-off invoices are excluded from this specific Billing fee calculation.
The percentage-based structure allows charges to vary with eligible billing activity.
Monthly subscription plans
Stripe publishes four US monthly Billing plans, each requiring a one-year contract:
- $620 per month: Up to $100,000 in monthly Billing volume
- $1,500 per month: Up to $250,000 in monthly Billing volume
- $2,950 per month: Up to $500,000 in monthly Billing volume
- $5,750 per month: Up to $1 million in monthly Billing volume
Each plan charges 0.67% on additional eligible Billing volume above its included allowance.
The fixed monthly structure provides a defined volume allowance, while the effective rate depends on how consistently a company uses that allowance.
Stripe also offers custom pricing for companies with larger billing volumes or specialized commercial requirements. Those arrangements depend on the applicable contract and product configuration.
Features included in Stripe Billing pricing
Subscription management and proration
Stripe Billing supports recurring charges across fixed-rate, per-seat, and tiered pricing configurations.
Subscription schedules allow businesses to plan changes to prices, quantities, discounts, and other subscription settings.
Proration settings determine how eligible mid-cycle adjustments affect invoices and customer balances.
These features support recurring subscription models, annual agreements, and planned commercial updates.
Usage-based billing and metering
Stripe's Meters API collects product usage events and aggregates them into billable quantities.
Supported metrics can represent activity such as:
- API requests
- Storage consumption
- Transaction counts
- Data processing
- Other configured product measurements
Standard Billing pricing includes basic usage-based billing with up to 100 million meter events per month.
This allowance is distinct from API request-rate limits and event-ingestion throughput. Stripe also provides meter-event adjustments for supported corrections.
Invoicing and revenue recovery
Stripe Billing provides recurring invoice generation, payment retries, automated reminders, and customer billing management.
Its hosted customer portal allows subscribers to manage payment methods and supported subscription settings.
Automatic reconciliation is also available for eligible recurring invoices paid through ACH credit or wire transfers.
These functions connect subscription management with payment collection and customer account workflows.
Additional Stripe fees beyond Billing
Credit card and ACH processing
Stripe Payments has a separate transaction fee structure.
Published standard US online payment rates include:
- Domestic card transactions: 2.9% plus $0.30
- International cards: An additional 1.5%
- Currency conversion: An additional 1% when required
- ACH Direct Debit: 0.8% per transaction, capped at $5
Actual charges depend on payment method, merchant location, transaction characteristics, and contracted rates.
The Federal Reserve Payments Study tracks US noncash payment activity, including card and bank payment instruments. Payment method distribution is relevant when evaluating collection costs across a recurring customer base.
Stripe Tax pricing
Stripe Tax provides automated tax calculation and collection through separately priced products.
Under Tax Basic, published US pricing includes:
- No-code integration: 0.5% per qualifying transaction where the merchant is registered to collect taxes
- API integration: $0.50 per qualifying transaction, including up to 10 calculation API calls, with additional calls charged separately
Stripe Tax Complete uses a different subscription-based pricing structure for broader tax administration capabilities.
Tax-related charges depend on the selected product and applicable transaction activity.
Stripe Revenue Recognition pricing
Stripe Revenue Recognition provides automated revenue accounting and reporting.
Its published US monthly plan begins at $25 for up to $10,000 in monthly payment volume, with a 0.25% overage rate.
Higher-volume annual subscription options have different allowances and overage rates.
Revenue Recognition fees are separate from Billing and Payments charges, making the selected combination of products relevant to total cost.
Advanced usage-based billing through Metronome
Metronome's role in Stripe's offering
Stripe completed its acquisition of Metronome in January 2026, expanding its usage-based billing capabilities.
Metronome supports advanced metering, pricing, and enterprise billing requirements, including:
- Usage-based, subscription, seat-based, and hybrid pricing
- SQL-based billable metrics
- Multidimensional pricing
- Enterprise commitments and credits
- Customer-specific rates
- Contract amendments
- Scheduled commercial changes
- Billing corrections
- Customer usage dashboards
These capabilities support companies whose billing models combine granular usage measurement with negotiated commercial terms.
Metronome pricing
Metronome publishes a Starter plan and offers a Custom plan for larger or specialized deployments.
The Starter plan charges:
- 0.8% of billing volume
- $0.04 per 1,000 ingested events
Its cost therefore depends on two separate variables: monetary billing volume and the number of ingested events.
The Custom plan uses quote-based pricing and adds capabilities such as Salesforce and NetSuite invoicing integrations, cloud marketplace integrations, data exports, and enhanced support.
Metronome's commercial arrangements are distinct from Stripe Billing's standard pricing. Applicable charges depend on the contracted products and services.
Understanding usage-based pricing requirements
Different pricing structures create different billing requirements.
Subscription pricing charges recurring fees for access or defined service periods. Usage-based pricing connects charges to measurable activity, while hybrid pricing combines multiple components, such as fixed platform fees and usage overages.
Credit-based pricing uses balances that customers purchase or receive and apply against eligible charges. Outcome-based pricing ties charges to defined results rather than usage alone.
For enterprise agreements, these models may also involve commitments, custom rates, contract phases, or negotiated discounts.
Billing configuration, usage instrumentation, and finance workflows depend on the commercial structure being implemented.
Stripe Billing API integration and operational costs
Implementing subscription and usage workflows
Stripe provides APIs, SDKs, webhooks, and prebuilt components for subscription billing.
Implementation can include:
- Product and price configuration
- Customer account synchronization
- Subscription lifecycle management
- Usage event instrumentation
- Billing metric definitions
- Event ingestion and adjustments
- Payment collection
- CRM and ERP integrations
The scope depends on the product architecture and complexity of the pricing model.
Standard recurring subscriptions and multi-product enterprise billing environments involve different integration and operational requirements.
Historical usage and billing corrections
Usage-based billing must accommodate late-arriving events, corrected usage records, and amended commercial terms.
Stripe provides meter-event adjustments, while Metronome supports granular usage data and additional billing correction workflows.
The applicable correction process depends on the product configuration, event history, and invoice state.
Historical corrections and price evolution are distinct operations. Corrections address recorded billing information, while price evolution concerns how future or eligible historical activity is priced under revised commercial terms.
Calculating Stripe Billing's total cost of ownership
A monthly cost example
Consider a hypothetical US SaaS company generating $100,000 in eligible monthly Billing volume from 1,000 domestic card transactions averaging $100 each.
Using the standard published pay-as-you-go rates:
- Stripe Billing: $700
- Percentage-based card processing: $2,900
- Fixed card processing charges: $300
- Combined monthly Billing and Payments fees: $3,900
This calculation excludes Stripe Tax, Revenue Recognition, disputes, optional products, and negotiated commercial terms.
It illustrates how Billing and Payments charges contribute separately to the overall cost of the same recurring revenue activity.
Factors affecting total costs
Beyond published platform fees, relevant cost components include:
- Billing volume: Revenue activity subject to applicable billing charges
- Payment distribution: Domestic cards, international transactions, ACH, and other payment methods
- Event volume: Usage records processed through the selected metering infrastructure
- Pricing complexity: Billable metrics, credits, commitments, and customer-specific contracts
- Engineering requirements: Usage instrumentation, integration, testing, and maintenance
- Finance workflows: Reconciliation, billing adjustments, collections, and reporting
The FinOps Foundation's framework for unit economics connects technology costs with measurable business activity.
For usage-based software, metrics such as cost per API request, transaction, or token can help companies analyze how product activity relates to revenue and operating costs.
This provides a broader financial perspective than the billing platform's percentage-based fee alone.
Finance workflows and revenue recognition
Connecting billing activity to financial records
Usage-based and hybrid pricing can involve subscriptions, prepaid credits, enterprise commitments, and customer-specific commercial terms.
Finance teams need records connecting contractual obligations, delivered services, invoice amounts, payments, and recognized revenue.
Applicable standards may include ASC 606 under US GAAP or IFRS 15 under IFRS Accounting Standards.
The IFRS Foundation's IFRS 15 requirements establish principles for recognizing revenue from customer contracts.
Billing and revenue recognition software can support the data and workflows used to apply these requirements.
Financial reporting and integrations
Stripe provides reporting and data export capabilities through products such as Revenue Recognition and Data Pipeline. Metronome also supports integrations with commercial and financial systems.
Relevant workflows include invoice creation, payment reconciliation, credit notes, accounts receivable, and financial reporting.
The operational structure depends on how billing data connects with the organization's CRM, ERP, and accounting systems.
How Orb supports usage-based billing and price evolution
Orb provides revenue infrastructure for companies managing usage-based and hybrid pricing. Its platform connects metering, pricing, billing, invoicing, and finance workflows across product, engineering, and finance teams.
Raw usage events and flexible pricing
Orb's usage-based billing engine uses raw usage events to calculate billable metrics.
This supports historical usage analysis, eligible backfills, billing adjustments, and price evolution.
Key capabilities include:
- Custom SQL metrics: Define billable quantities through configurable calculations over usage data
- Hybrid pricing: Combine subscriptions, seats, fixed fees, and usage-based charges
- Dimensional price groups: Support pricing across dimensions such as region, instance type, and environment using a single pricing configuration for dimension combinations
- Prepaid credits: Manage credit balances, consumption, and expiration
- Hosted Rollups: Aggregate configured high-volume event streams during ingestion
These capabilities support companies managing multiple products, granular usage metrics, and evolving pricing structures.
Historical pricing simulations
Orb Simulations allows teams to model proposed pricing against real historical usage before production rollout.
Product and finance teams can compare pricing scenarios, evaluate customer-level effects, and model projected revenue changes.
These simulations support data-driven pricing decisions without treating modeled outcomes as guaranteed future results.
Orb's price evolution capabilities also provide centralized tools for managing customer-specific pricing, scheduled updates, and subscription migrations.
Invoicing and finance workflows
Orb connects usage-based billing with invoicing, collections, accounts receivable, and financial reporting through its finance workflows capabilities.
Its NetSuite integration creates standard transaction objects, including invoices, credit memos, and customer deposits, supporting established finance workflows.
Orb's Experience Kit supports customer-facing billing experiences, including usage visibility and configurable interfaces. Its spend controls provide alerts and automated workflows that help customers monitor usage and spending.
Published customer stories illustrate specific operational outcomes:
- Vercel: Reported an 80% reduction in time required to build and launch billing for new products
- Stytch: Reported a 75% reduction in time spent processing bills and invoicing
These figures reflect the respective customer implementations rather than guaranteed performance outcomes.
Orb pricing structure
Orb pricing is customized across three plans:
- Core: Real-time event ingestion, hybrid and usage-based billing, invoicing, and finance and tax integrations
- Advanced: Adds data warehouse synchronization, Salesforce, NetSuite, customer hierarchy capabilities, and premium support
- Enterprise: Adds enterprise-grade service-level agreements and dedicated support
Pricing is based primarily on billings and event volume, with additional platform fees for Advanced and Enterprise plans.
Orb also connects with payment-processing infrastructure, including Stripe Payments, allowing billing execution and payment collection to operate through the configured revenue stack.
Frequently asked questions
What counts toward Stripe Billing volume?
Stripe Billing volume includes eligible recurring Billing transactions processed through Stripe or supported external payment arrangements. One-off invoices are excluded from the specific volume calculation used for standard Billing fees.
How do Stripe Billing and Stripe Payments differ?
Stripe Billing manages subscriptions, billing calculations, invoices, and recurring revenue workflows. Stripe Payments processes transactions and payment collection through supported payment methods. The products have distinct pricing structures and can operate together.
Can Stripe support hybrid and credit-based pricing?
Yes. Stripe Billing supports subscriptions, metered usage, and billing credits. Metronome extends the offering with advanced hybrid pricing, commitments, negotiated contracts, and credit-based arrangements.
What affects usage-based billing costs at scale?
Important factors include the number of ingested events, billing volume, selected pricing model, customer contracts, payment methods, integrations, and finance operations. The relative impact of each factor depends on the deployed billing infrastructure and commercial agreement.
How does Orb support price evolution?
Orb supports price evolution through retained raw usage events, configurable billable metrics, historical pricing simulations, scheduled pricing updates, and connected billing workflows. These capabilities allow product and finance teams to evaluate proposed pricing against historical usage and manage commercial updates within Orb's revenue infrastructure.