Polar.sh has established itself as a merchant of record platform designed for indie developers and open source projects, handling payments and cross-border tax obligations in a developer-friendly package. However, as software companies scale beyond simple subscription models into usage-based pricing, prepaid credits, and enterprise contracts, they often need billing infrastructure that goes deeper than what a merchant of record provides. For teams building AI products, cloud infrastructure, or developer tools with usage-based revenue models, the right usage-based billing engine can mean the difference between pricing that scales with value delivery and pricing that holds back growth.
This guide examines eight alternatives to Polar.sh, starting with platforms built for complex billing scenarios and covering the full spectrum of merchant of record and billing infrastructure options.
Key takeaways
- Merchant of record platforms handle applicable tax obligations: Polar.sh, Lemon Squeezy, and Paddle act as the seller of record, managing applicable sales tax, VAT, and chargebacks for supported transactions
- Transaction fee structures vary by provider: Merchant of record platforms typically charge percentage-based transaction fees plus fixed per-transaction amounts, while billing platforms use different pricing models based on billed revenue, event volume, or subscription tiers. Polar updated its Starter pricing for new organizations in May 2026, while eligible existing organizations retained grandfathered pricing
- Usage-based billing requires infrastructure beyond basic merchant of record capabilities: Companies billing for API calls, tokens, compute time, or storage need real-time metering, dimensional pricing, and retroactive correction capabilities that extend beyond transaction processing
- SQL-based metrics support flexible pricing models: Platforms like Orb allow teams to define billable metrics using SQL queries against raw usage events, enabling complex aggregations like averages, maximums, and custom calculations without rebuilding application billing logic for each change
- Enterprise finance requirements extend beyond invoicing: Revenue recognition reporting aligned with accounting standards, AR aging reports, and native ERP integrations become critical as companies scale past early-stage billing needs
1) Orb
Orb provides usage-based billing infrastructure for SaaS companies, AI platforms, and cloud infrastructure providers that have outgrown simple subscription models. Rather than acting as a merchant of record, Orb focuses on the billing logic layer, integrating with payment processors like Stripe and Adyen to handle the complexity between raw usage events and accurate invoices.
Core capabilities
- Real-time usage metering: Ingest high volumes of raw usage events through an idempotent API, with transformation and aggregation capabilities while retaining granular event data for billing and analysis
- SQL-based billable metrics: Define billing metrics using SQL queries, enabling complex calculations like weighted averages, tiered maximums, and custom aggregations without rebuilding application billing logic for each change
- Pricing simulations: Test pricing changes against historical customer usage before deploying, seeing projected revenue impact based on historical usage across customer segments
- Dimensional price groups: Price across multiple usage dimensions, such as region, instance type, and environment, using a single pricing configuration for dimension combinations
- Prepaid credits: Support platform-wide credits, SKU-scoped credits, credit expiration, and automated drawdown tracking with accounting records
- Backfills and corrections: Orb retains raw usage events to support eligible historical backfills and backdated adjustments. Affected draft invoices can be recalculated, while finalized invoices remain unchanged and use supported correction workflows to maintain an auditable billing record
Enterprise finance features
Orb addresses the finance workflow requirements that emerge as companies scale:
- Revenue recognition: Revenue recognition reporting with recognized, deferred, and unbilled revenue views supporting ASC 606 accounting workflows
- NetSuite integration: Creates native transaction records including invoices, credit memos, and customer deposits, with sales-order support for applicable workflows
- AR aging and collections: Accounts receivable automation with payment retry logic and configurable dunning workflows
- Accounting period locks: Prevent retroactive changes to closed periods, with subsequent adjustments handled through supported workflows
Use cases
Orb serves AI companies billing for tokens and inference, cloud infrastructure providers with multi-dimensional usage, developer platforms with freemium-to-paid conversion flows, and enterprise software transitioning from seat-based to usage-based models.
Customers report measurable outcomes from implementing Orb. Vercel achieved an 80% reduction in time required to build and launch billing for new products. Stytch reduced time spent processing bills and invoicing by 75%. Orb reports that Replit has seen 40x revenue growth since using Orb to monetize usage.
Technical foundation
Orb's architecture differs from merchant of record platforms in a fundamental way: its standard ingestion architecture retains raw usage events rather than only aggregated data. This supports historical backfills, eligible backdated pricing adjustments, and recalculation of affected draft invoices. Finalized invoices use separate correction workflows. The platform processes 1.5 million+ invoices per month for Supabase and offers a 99.9% availability SLA for Enterprise accounts.
For enterprise security and finance workflows, Orb maintains SOC 1 and SOC 2 Type II reports, supporting financial reporting controls and data security requirements.
Pricing structure
Orb offers a Business plan at \$6 per credit, with volume discounts available, and an Enterprise plan with custom pricing. Credits are consumed based on billings processed ($1,000 in billings = 1 credit), raw usage events ingested (200,000 events = 1 credit), and other usage meters detailed in the consumption table. Enterprise includes expanded finance workflows, customer hierarchies, advanced controls, and a 99.9% availability SLA. A separate paid Enterprise Support Bundle offers dedicated support services and a 99.99% SLA commitment. New Business accounts receive 100 free credits.
When Orb fits usage-based billing
Orb is a strong choice for companies evolving beyond straightforward subscription billing. For businesses that need complex usage-based pricing with multiple dimensions, want to experiment with pricing changes before deployment, require enterprise contract support with commitments and minimums, or need revenue recognition reporting aligned with accounting standards, Orb provides the billing infrastructure to support these requirements while integrating with existing payment processors.
2) Lemon Squeezy
Lemon Squeezy operates as a merchant of record platform designed for creators and developers selling digital products. The platform handles payment processing, applicable tax obligations, and fraud protection in a single package.
Core capabilities
- Merchant of record: Acts as the seller of record, handling sales tax, VAT, and chargebacks for supported transactions
- Storefront builder: Includes built-in checkout pages and product storefronts without requiring a separate website
- Digital product delivery: Manages license keys, file downloads, and access control for digital goods
- Subscription management: Supports recurring billing and subscription lifecycle management
- Affiliate program: Built-in affiliate management for creators building distribution networks
Use cases
Lemon Squeezy serves creators selling courses, ebooks, templates, and software licenses. The platform focuses on digital product sales, storefronts, checkout, and subscriptions.
Considerations
Lemon Squeezy was acquired by Stripe in 2024. In January 2026, the company outlined its focus on Stripe Managed Payments and plans to help existing Lemon Squeezy customers migrate to that offering.
Lemon Squeezy also offers usage-based billing features, while its broader product focus includes merchant of record services, digital product sales, and subscription management.
3) Paddle
Paddle provides merchant of record services for SaaS companies, handling global tax compliance, payment processing, and subscription management. The platform has operated since 2012.
Core capabilities
- Global tax compliance: Manages applicable sales tax, VAT, and GST obligations for supported transactions across 200+ countries and territories
- Subscription lifecycle: Supports upgrades, downgrades, pauses, and cancellations with proration handling
- B2B invoicing: Generates invoices for enterprise customers with payment terms
- Checkout optimization: Provides localized checkout experiences with currency conversion and regional payment methods
- Revenue recovery: Includes dunning management and payment retry logic
Use cases
Paddle serves SaaS companies selling subscriptions globally that use merchant of record services for tax compliance and payment operations. The platform combines international payment processing, subscriptions, and checkout workflows.
Considerations
Paddle's merchant of record model means the platform acts as the seller of record for covered transactions. Customers purchasing through Paddle receive invoices identifying the merchant of record.
Paddle has introduced native usage-based billing capabilities, currently available through an early-access beta program. Its supported metering and reporting functionality differs from dedicated usage-based billing engines.
4) Stripe Billing
Stripe Billing extends Stripe's payment processing platform with subscription management and usage-based billing features. Unlike merchant of record platforms, Stripe Billing does not itself assume the seller's tax obligations. Tax calculation and related workflows can be supported through Stripe Tax or third-party integrations.
Core capabilities
- Subscription management: Supports fixed-price subscriptions with proration, trials, and plan changes
- Usage metering: Provides the Stripe Meters API for reporting consumption against subscription items
- Invoice generation: Creates and sends invoices with customizable templates and branding
- Payment methods: Supports cards, ACH, SEPA, and other payment methods through the core Stripe infrastructure
- Developer experience: Offers APIs, SDKs, and documentation within the broader Stripe ecosystem
Use cases
Stripe Billing serves companies already using Stripe for payment processing that want to add subscription functionality within the same ecosystem. The platform integrates with Stripe Payments and other Stripe products.
Considerations
Stripe Billing provides usage metering through its Meters API. More complex usage-based billing capabilities, including enterprise contract management and multidimensional rates, are also offered through Metronome, a Stripe product.
For AI companies billing for tokens or cloud platforms with complex consumption patterns, specialized usage metering infrastructure offers additional options for pricing execution.
5) Dodo Payments
Dodo Payments operates as a merchant of record platform supporting international payments, including local payment methods used in India, Southeast Asia, and Latin America.
Core capabilities
- Regional payment methods: Supports UPI, local bank transfers, and regional payment options alongside cards
- Merchant of record: Handles applicable tax obligations and acts as the seller of record for supported transactions
- Subscription and usage billing: Provides recurring billing, prepaid credits, and usage metering for software products
- Multi-currency support: Processes payments in supported currencies with conversion handling
Use cases
Dodo Payments serves SaaS companies and AI startups selling internationally, including businesses accepting UPI and local payment methods in Asian markets. The platform combines merchant of record services with subscription, credit, and usage billing.
Considerations
Dodo Payments supports both payment collection and usage-based billing. Its pricing varies by payment method, transaction geography, and billing model.
The platform launched in 2024 and has continued expanding its payment and billing features.
6) Creem
Creem operates as a merchant of record platform for SaaS developers, with transaction-based pricing for digital products and subscriptions.
Core capabilities
- Merchant of record: Handles tax compliance and fraud protection as the seller of record
- Subscription billing: Supports recurring payments with subscription management
- Usage-based billing: Provides credit wallets, usage metering, and consumption-based pricing
- Checkout pages: Provides hosted checkout experiences for product purchases
- License key delivery: Manages software license distribution for digital products
Use cases
Creem serves developers and small teams selling SaaS products or digital goods through merchant of record services. The platform provides payment processing, tax handling, subscriptions, and usage-based billing features.
Considerations
Creem offers a standard transaction-based plan alongside additional services for larger or more specialized operations. Its platform includes credit wallets, usage metering, and support for subscription billing.
7) FastSpring
FastSpring provides merchant of record services focused on global payment processing, tax administration, and subscription management for software companies and digital product sellers.
Core capabilities
- Merchant of record: Acts as the seller of record, managing applicable tax obligations across jurisdictions including VAT, GST, and sales tax under cross-border VAT requirements
- Global payment processing: Supports multiple payment methods including cards, PayPal, bank transfers, and regional options
- Subscription management: Handles recurring billing, upgrades, downgrades, and billing lifecycle events
- B2B invoicing: Generates invoices for enterprise customers with purchase order workflows and payment terms
- Localization: Provides currency conversion, localized checkout experiences, and regional payment method support
Use cases
FastSpring serves software companies selling globally that use merchant of record services for tax and payment management, including businesses with B2B invoicing requirements.
Considerations
FastSpring's transaction costs vary according to its revenue-sharing arrangements and the merchant's payment volume.
The platform provides merchant of record services covering payment processing, subscriptions, and invoicing. Its available billing configurations determine how specific usage-based pricing requirements are supported.
8) Chargebee
Chargebee operates as a billing platform that supports subscription management, usage-based pricing, and integrations with multiple payment gateways rather than acting as a merchant of record.
Core capabilities
- Subscription and usage billing: Supports recurring subscriptions, usage metering with custom SQL meters, and hybrid pricing models
- Payment gateway integrations: Integrates with 40+ payment gateways including Stripe, Braintree, and PayPal
- Billing lifecycle management: Handles upgrades, downgrades, proration, trials, and billing automation
- Invoicing and payments: Generates invoices, manages payment collection, and supports multiple payment methods
- Revenue recognition: Provides revenue recognition reporting supporting workflows under revenue recognition standards
Use cases
Chargebee serves SaaS companies that use subscription and usage-based billing while maintaining relationships with payment processors. Tax calculation and reporting can be supported through integrations with tax services.
Considerations
Unlike merchant of record platforms, Chargebee does not become the seller of record for customers' transactions. Businesses using Chargebee remain responsible for applicable tax obligations, supported by tax service integrations and internal processes.
Chargebee supports SQL-based usage metering, subscription management, and financial reporting, with advanced capabilities depending on the selected plan.
Why Orb stands out for usage-based billing
The fundamental distinction between Orb and merchant of record platforms comes down to what problem each solves. Merchant of record platforms focus on accepting payments and handling applicable tax obligations globally. Orb addresses a different requirement: accurately billing customers based on their actual product usage.
Beyond transaction processing
When software companies adopt usage-based or hybrid pricing models, billing becomes significantly more complex than processing recurring subscription payments. Consider the billing requirements for an AI company charging per token:
- Event ingestion at scale: Processing millions of API calls per day and converting them into accurate billing records
- Multi-dimensional metering: Tracking usage across models, contexts, and customer tiers simultaneously to support granular cost allocation
- Real-time visibility: Providing customers with current usage data so they can manage spend effectively
- Retroactive corrections: Handling late-arriving events and billing adjustments through supported draft-invoice and finalized-invoice workflows
- Credit management: Supporting prepaid credit pools with expiration, scoping, and automated drawdown
Merchant of record platforms handle payment-related responsibilities, while Orb provides usage-based billing infrastructure that retains raw usage events and supports complex aggregation and pricing execution.
The raw data layer advantage
Orb's standard ingestion architecture retains raw usage events rather than discarding them after aggregation. This approach supports:
- Historical price modeling: Run pricing simulations against actual customer usage to see projected revenue impact before deploying changes
- Backdated adjustments: Apply eligible pricing changes to historical periods, with draft invoice recalculation and supported correction workflows for finalized invoices
- Invoice traceability: Trace usage-based invoice line items to the underlying event data
- Flexible aggregation: Change how billable metrics are calculated while retaining the underlying usage data
Enterprise finance alignment
As companies scale, finance team requirements extend beyond generating invoices. Revenue recognition, AR management, and ERP integration become critical operational needs. Orb's finance workflows address these requirements with native NetSuite integration that creates transaction records, revenue recognition reporting that supports audit processes, and AR aging with collections automation.
When to graduate from merchant of record
Companies may adopt specialized billing infrastructure as their pricing and financial operations become more complex:
- Transaction fees affect economics at scale: As revenue grows, the total cost of percentage-based transaction fees becomes more significant. Billing platforms use different pricing models, making the economics depend on factors such as event volume and billings processed
- Pricing complexity exceeds basic transaction processing: Multi-dimensional pricing, custom aggregations, usage commitments, and enterprise contracts require configurable billing logic
- Finance teams need reporting and audit controls: Revenue recognition reporting, deferred revenue tracking, and ERP integration become important finance workflow requirements
- Engineering time on billing grows: Building custom billing logic on top of basic payment APIs consumes engineering resources that could support product development
For companies at this inflection point, Orb provides the billing infrastructure to support sophisticated pricing while integrating with existing payment processors for transaction processing.
Frequently asked questions
What is the difference between a merchant of record and a billing platform?
A merchant of record acts as the legal seller for supported transactions, handling applicable tax obligations, fraud protection, and chargebacks. Businesses receive payouts after the merchant of record deducts fees and handles applicable tax remittance. A billing platform like Orb focuses on the logic layer between usage events and invoices, calculating what customers owe based on their consumption, generating invoices, and managing billing lifecycle events. Billing platforms typically integrate with payment processors rather than acting as the payment layer themselves.
Can Orb work with existing payment processors?
Yes. Orb integrates with payment processors including Stripe and Adyen rather than replacing them. This architecture allows companies to maintain their existing payment infrastructure while adding usage-based billing capabilities. Orb handles metering, pricing calculation, invoicing, and revenue recognition reporting, while the payment processor manages transaction processing and fund collection.
How does SQL-based billing work?
Orb allows teams to define billable metrics using SQL queries against raw usage events. Instead of being limited to simple event counts, teams can create billing metrics based on averages, maximums, weighted calculations, and supported SQL-based aggregations. For example, an infrastructure company could bill based on the 95th percentile of CPU usage rather than total CPU-seconds, aligning pricing more closely with the value customers receive. SQL-based configurations allow billing metric changes without rebuilding application billing logic for every revision.
What compliance certifications does Orb maintain?
Orb maintains a SOC 1 Type II report addressing controls relevant to financial reporting for companies whose billing data feeds into audited financial statements. The platform also maintains a SOC 2 Type II report covering applicable trust services criteria related to security and data protection. These independent examinations support enterprise procurement and provide assurance about relevant controls.
How long does Orb implementation typically take?
Implementation timelines depend on pricing complexity, usage instrumentation, integrations, and historical data migration. Orb provides an API-first platform with SDKs and implementation support. In Orb's published customer story, Replit implemented Orb in one month with one engineer. More extensive projects vary according to requirements and deployment scope.

