Billing Software in 2026: What Changed This Year

In 2026, the billing software market consolidated around usage-based pricing for AI products: Stripe completed its purchase of Metronome in January, and Adyen's acquisition of Orb was announced in June and closed in July. This article covers what was reported this year, what the vendors' own docs show, and what buyers should do differently.

The Headline: Two Processor Acquisitions

Two reported deals defined billing software in 2026, and they rhyme. Stripe completed its purchase of Metronome — the usage-based billing specialist — on January 14, 2026, per industry reporting. Adyen's acquisition of Orb — another usage-metering specialist — was announced on June 11, 2026 and closed on July 1, 2026, per the same reporting and Lago's writeup of the announcement.

The shared logic is visible in what both targets do: metered, event-based billing for consumption-priced products — the pricing shape AI products overwhelmingly use. Payment processors buying the metering layer is the market's way of saying that deciding what gets billed is now as strategic as moving the money.

A note on sourcing before we go further: deal details below come from third-party reporting and vendor-authored posts, cited as such. Figures and framings from interested parties are attributed rather than stated as neutral fact. Verify anything deal-specific against primary announcements before making vendor decisions on it.

Stripe and Metronome

The most concrete, documentation-verifiable effect of the Metronome deal is architectural: Stripe's own subscription documentation now points usage-based billing at Metronome, stating "Use Metronome to configure more complex pricing models" in its pricing design guide. Usage billing has effectively become a separate Stripe product conversation from subscription billing.

What this means in practice:

• If your pricing is subscription-based (flat-rate, per-seat, tiered), Stripe Billing continues as documented — its published pay-as-you-go rate is 0.7% of billing volume with annual plans starting at $620/month, per Stripe's pricing page. Nothing in the reporting suggests that changed.
• If your pricing is consumption-based — tokens, API calls, compute — you are now evaluating two Stripe products, not one: Billing for subscriptions and Metronome for metering and rating. Budget and implementation planning should reflect that split rather than assuming one quote covers both.
• Metronome's roadmap now belongs to Stripe. For Stripe-native companies that is mostly good news (tighter integration, more resources). For multi-processor companies it is a strategic question: how much of your billing logic do you want on one processor's roadmap?

The broader signal is about where the industry thinks pricing is going. When the largest payment processor buys a usage-billing specialist, it is betting that consumption-based pricing keeps spreading beyond AI into mainstream SaaS. Our usage-based billing explainer covers the mechanics for teams considering the shift.

Adyen and Orb

Adyen's Orb acquisition, announced June 11 and closed July 1, 2026, follows the same playbook from the processor side: Orb's engine handles event-based usage metering and rating, and Adyen — a payments company — now owns it. The reporting frames the deal as converging billing and payments into closer infrastructure, with the familiar promise that billing data can feed back into payment performance.

The evaluation question this raises is processor neutrality: Orb was positioned as a metering layer independent of any single payment provider. Post-acquisition, buyers who valued that independence need explicit answers about where the metering logic lives long-term and what happens to multi-processor support. Lago's team — writing as an interested competitor, so read it as their argument rather than neutral fact — made exactly this point in response to the June 11 announcement, contrasting their own self-hostable position with Orb's managed, cloud-only one.

Two acquisitions do not make a law, but the pattern is now unmistakable: the independent metering specialists are being absorbed by processors. Whether that is good for you depends entirely on whether you want your metering coupled to your payments.

Chargebee's 2026 Moves

Outside the two mega-deals, the most documented 2026 move from a major subscription platform is Chargebee's: a May 2026 partnership with Avalara for tax automation, reported alongside an emphasis on AI monetization in Chargebee's positioning. The pairing is telling — as pricing gets more usage-shaped, the two hardest adjacent problems are tax on variable invoices and metering itself.

The practical read for buyers: subscription platforms are not standing still while processors buy metering specialists. Expect the established billing vendors to deepen usage-billing support, tax automation, and AI-pricing tooling through 2026 — and evaluate their roadmaps against the processor-owned alternatives rather than assuming the category froze in 2024.

Open Source in 2026: Licenses and the Independence Argument

The acquisitions sharpened the open-source counterargument: if you self-host your billing logic, no acquisition can move it onto someone else's roadmap. The 2026 reporting gives a current license map: Lago and Flexprice are AGPL-3.0 licensed, while OpenMeter and Kill Bill use Apache-2.0, per the same industry comparison — which also frames the core trade-off as self-hosted operational cost versus managed percentage-based pricing.

The license distinction matters in practice:

• AGPL-3.0 (Lago, Flexprice) is copyleft: if you modify the code and run it over a network, you generally must share your modifications. Most companies using rather than modifying the software are unaffected, but legal teams often scrutinize AGPL — clear it before committing.
• Apache-2.0 (OpenMeter, Kill Bill) is permissive: use, modify, and embed with minimal obligations.

And the cost trade-off is honest on both sides: self-hosting eliminates the vendor's percentage fee but creates permanent operational cost — deployment, upgrades, monitoring, incident response for a revenue-critical system. Managed platforms charge the percentage but absorb all of that. Our open-source vs. hosted comparison works through the full accounting.

What Hasn't Changed for Buyers

For all the deal-making, the fundamentals of buying billing software are unchanged:

• Published pricing still favors transparency at the low end. Stripe's 0.7% pay-as-you-go rate remains public on its pricing page; most competitors still go quote-only above modest thresholds. Verify current numbers on pricing pages — our crossover math still applies.
• Billing-layer cost is still not processing cost. None of the 2026 deals changed the underlying economics: you pay for the billing software and for moving money, separately or bundled. Compare accordingly.
• Dunning, tax, and metering reliability remain the unglamorous differentiators. Acquisitions make headlines; failed-payment recovery rates and accurate event ingestion make or break finance teams. Evaluate those with the same seriousness as the deal narrative.
• Migrations are still migrations. Consolidation does not make switching platforms easier — if anything, deeper processor integration raises switching costs. Our migration guide covers the staged approach.

What to Do Differently Now

1. If you are choosing a usage-billing stack today, evaluate the processor relationship explicitly. Metronome-inside-Stripe and Orb-inside-Adyen are serious products; just decide with eyes open whether you want your metering on a processor's roadmap.
2. Price the metering separately. With usage billing increasingly a separate product and sales conversation, get its pricing in writing rather than assuming it is included in the billing platform quote.
3. Revisit shortlists built before 2026. Advice from 2024 predates both acquisitions and the resulting packaging changes. See our startup guide for current positioning.
4. Ask the neutrality questions directly. If you change payment processors in three years, what happens to your billing logic, metering pipelines, and historical data? Is the metering engine a standalone product with its own roadmap, or a feature of the processor's suite?
5. Keep an exit lens. Ask every vendor how you get your data — and your billing logic — out. In a consolidating market, portability is a feature.

FAQs

What was the biggest billing software news of 2026?

Two reported acquisitions: Stripe's purchase of usage-billing specialist Metronome (completed January 14, 2026) and Adyen's acquisition of Orb (announced June 11, 2026, closed July 1). Both involve payment processors buying the metering layer for consumption-based pricing.

Is usage-based billing still part of Stripe Billing?

For complex cases, Stripe's own documentation now points to Metronome: "Use Metronome to configure more complex pricing models." Stripe Billing continues to handle subscription billing (flat-rate, per-seat, tiered) as documented.

What does the Adyen–Orb acquisition mean for Orb customers?

What is documented: the deal was announced June 11 and closed July 1, 2026. Beyond that, treat vendor statements and competitor commentary (including Lago's response post) as positioned rather than neutral, and ask Adyen directly about roadmap and multi-processor support.

What open-source billing options exist in 2026?

Current reporting names Lago and Flexprice (AGPL-3.0) and OpenMeter and Kill Bill (Apache-2.0). The trade-off versus managed platforms is self-hosted operational cost against percentage-based vendor pricing — see our open-source vs. hosted comparison.

Has billing software pricing changed in 2026?

Published pricing structures look stable — Stripe's 0.7% pay-as-you-go rate was verified on its pricing page in September 2026. What changed is packaging: usage billing is increasingly a separate product with separate pricing, so confirm what any quote includes.

Should 2026 news change which platform I choose?

It should change the questions, not necessarily the answer. Add processor neutrality, metering packaging, and exit portability to your evaluation — then pick on the fundamentals: your pricing model, verified pricing, dunning, tax, and migration cost.

Conclusion

2026 was the year billing software consolidated around usage-based pricing: the processors bought the metering specialists, open source sharpened its independence pitch, and "where does my billing logic live in five years" became a question every buyer should ask. None of it changes the fundamentals — match the platform to your pricing model, verify pricing on the vendor's page, separate billing cost from processing cost — but it does change the shortlist questions. Evaluate the processor relationship, price metering separately, and keep an exit lens. For the evergreen versions of these decisions, see our Stripe Billing review, Chargebee review, and buyer's checklist.