Picking usage-based billing now that Stripe owns Metronome and Adyen owns Orb
Stripe closed its acquisition of Metronome on 14 January 2026. Adyen closed its acquisition of Orb on 1 July. So the two metering engines most AI and API companies shortlisted are now owned by companies whose main business is processing your payments. If you're pre-revenue and about to put a usage meter on your product, that's worth ten minutes of thought before you write the integration.
What actually changed
Nothing broke on day one. Stripe's announcement talks about integrating Metronome's metering with Stripe Billing. Adyen says Orb keeps running under an "incubator model" and keeps supporting other processors during the first phase, with the stated long-term intent being "a single infrastructure experience for merchants across billing and payments." Orb's own post says customers can keep their preferred processor.
Read those together and the direction is clear. Billing is turning into a feature of your payment processor again. That's fine if you were going to stay on that processor anyway. It's a cost if you wanted the freedom to move.
The founder's version of the decision
Most early teams don't need a metering engine yet. You need one when the thing you charge for is a volume (tokens, API calls, GB-months, minutes) and the numbers get big enough that summing them in your own database becomes a project. Before that, a flat plan plus a usage cap, or a few tiers, is easier to sell and easier to explain on a pricing page.
When you do need metering, the real choice is between three shapes:
- Processor-native. Stripe Billing with meters (and now Metronome behind it), or whatever your merchant of record ships. Fewest moving parts. Your pricing logic is coupled to that processor.
- Processor-owned but nominally neutral. Orb today. Strong engine, and the neutrality is a promise with an "initially" attached. Get the multi-processor terms in writing if you care.
- Independent or open source. Lago is the obvious one left. You own more of the plumbing, and some features you'll want for custom deals sit in paid tiers, so check the price page before you assume open source means free.
Questions to ask before you sign
Can it model your hardest meter live? Storage billed per GB-month needs a time-weighted aggregation, not a sum. Ask every vendor to build your trickiest meter in the demo. Most of the pain in billing migrations comes from one meter that turned out to be special.
What does "credits" mean to them? Credits applied to an invoice and a prepaid balance that usage burns down are different features. If it's a balance, ask whether it draws down in real time or only when the invoice finalizes. The second one lets a customer blow past their balance mid-cycle.
How are customer-specific deals stored? A negotiated rate on the contract and a coupon stacked on list price produce different invoices and different revenue reports. Early on you'll do a lot of both, for design partners and launch-week signups.
How hard is leaving? Ask for an export of customers, plans, meters and invoice history in a format another system can import. If the answer is "talk to support", price that in.
Where discounts fit
Whatever you pick, keep discounts as real objects in the billing system: a coupon or promotion code with a duration, a cap and an expiry. Don't make them a note in a spreadsheet or a manual credit. Real objects are auditable, they expire on their own, and other tools can read them. That's how Dealpuffin works: we read coupons from Stripe, Paddle or Polar, and the caps and expiry come from the provider, not from us. If your discounts live in your billing system, you can move them to any directory, marketplace or agent later.
Frequently asked questions
Is Metronome still available on its own?
Metronome is part of Stripe since January 2026. Check Stripe's current docs for how new integrations are routed between Stripe's native meters and Metronome before you build.
Does Orb still work with Stripe?
Adyen and Orb say Orb continues to support other payment processors during the first phase after the acquisition. The long-term stated goal is convergence with Adyen's payments, so ask about multi-processor support in your contract.
Do I need usage-based billing at launch?
Usually not. If your costs scale with usage, a flat plan with a clear cap protects your margin while you learn what customers actually use. Add metering when the cap starts costing you deals.
Related on Dealpuffin
For founders pricing a launch offer: How to read a SaaS discount page and Why target early adopters.