It depends on whether metering is your pricing foundation or a variable line on a subscription invoice. ChargeOver usage-based pricing and metered subscriptions work the second way: you post usage to a line item through its REST API, usage URLs, or a spreadsheet, and ChargeOver charges it against the invoice period. That suits recurring billing with a usage component, and it's a different architecture from a metering-first platform.

P.S. Every ChargeOver claim here comes from ChargeOver's own pricing, feature, documentation or security pages, checked on 13 August 2026. Where ChargeOver doesn't publish something, this page says "not listed" rather than inferring a limitation.

Key Takeaways

• ChargeOver bills metered usage at invoice time, against a line item carrying a usage value and from and to timestamps.

• ChargeOver starts at $229 a month, priced by paying-customer count, with no per-transaction fee and no percentage of revenue.

• ChargeOver's security page lists PCI DSS Level 1 and US data centers, and no page publishes a throughput or rate limit figure.

• Flexprice runs up to 1 million events per second, deployable in your own VPC, on-prem, or on Flexprice's managed cloud.

• Simplismart reclaimed 30% of its engineering bandwidth on Flexprice, and Segwise shipped credit billing in 3 days.

What does ChargeOver support for usage-based pricing and metered subscriptions?

ChargeOver accepts metered usage and bills it on a subscription foundation. Its own pages, checked 2026-08-13:

• Usage arrives via the REST API, usage URLs, or spreadsheets, as often or as rarely as you send it.

• Charges compute "based on the invoice date and period for which the customer is being billed", so the invoice run does the math.

• Unit pricing takes a base fee plus a per-unit rate, with tiers by volume. The worked example prices minutes at $0.05.

• Not listed on its pricing, feature, or security pages: throughput figures, support response times, an uptime SLA, SOC 2, SAML SSO, RBAC, non-US residency, self-hosting, credit wallets, entitlements, or contract versioning.

What should an enterprise check before buying usage-based billing?

These checks decide it, and none start with a vendor name.

1. Does the vendor publish a throughput and latency figure? ChargeOver publishes none.

2. Can it answer an entitlement or balance question in real time, rather than at invoice time?

3. Are credit wallets a primitive with recurring grants and rollover, or something your team builds?

4. Can it run inside your infrastructure, and where does the data live?

5. What's the P0 response time, in writing, with a number in it?

Our breakdown of enterprise billing software runs these checks across more vendors.

How do ChargeOver and Flexprice compare on enterprise usage-based billing?

Every cell comes from the vendor's own pages, checked 2026-08-13, or reads "not listed".