Adyen Buys Orb: Why a Payments Processor Wants the Billing Layer

Adyen just spent $335M to own something most payment processors do not even touch: the billing layer.

On 11 June 2026, Adyen announced a definitive agreement to acquire Orb, an enterprise billing platform built for usage-based and consumption pricing. Together with the Talon.One acquisition announced in April, that is more than a billion dollars of M&A in a few months from a company that had made no acquisitions at all in its first 20 years.

Ingo Uytdehaage, Co-CEO of Adyen: “The structural complexity of modern billing has become the kind of infrastructure problem Adyen is built to take on. Combining Orb’s billing product with Adyen’s payments platform closes the loop between what merchants charge and how those charges perform.”

Alvaro Morales, CEO of Orb: “Billing at serious scale is only half the equation. The other half is moving money across markets, currencies and enterprise requirements.”

Where Billing Sits in the Revenue Stack

For an enterprise merchant, getting paid involves more than processing a card. The full revenue lifecycle looks like this:

1. Metering: counting what the customer used (API calls, tokens, gigabytes, transactions).
2. Rating: applying the price plan, tiers, discounts and commitments.
3. Invoicing: producing the bill.
4. Authorization and collection: charging the card or pulling from the bank account.
5. Settlement: moving the funds to the merchant.
6. Reconciliation: matching what was billed with what was collected.

Processors have traditionally owned steps 4 and 5. Orb owns 1 through 3. Buying it moves Adyen upstream from “authorize and settle” to “meter, rate, invoice, reconcile.”

Why This Matters

AI-native companies do not bill by seat

AI companies bill by token, API call or outcome. That pricing is hard to run on billing systems built for monthly subscriptions. Processors handle money movement but not the metering layer above it. Orb closes that gap, and every AI company Adyen serves is a potential buyer.

It is a revenue lifecycle play

Once a merchant runs billing on the same platform as payments, switching processors means re-platforming billing too. That is a much stickier relationship than processing alone. It also gives Adyen data on what the merchant charges, not only on what gets authorized.

Variable billing makes authorization harder

This is the part payments teams should watch closely. With a fixed subscription, the amount is predictable and issuers are used to seeing it. With usage-based billing, the amount changes every cycle, sometimes sharply. Issuers may treat a much larger than usual charge as suspicious. Retry logic, dunning flows and authorization optimization all have to be coupled to the billing engine.

A failed payment on a variable invoice hits differently from a failed fixed subscription charge. The retry schedule, the customer message and even whether to split the charge depend on what was billed and why. That coupling is much easier when billing and payments sit on one platform. I cover retry and dunning design in Subscription Payment Retry Logic and Dunning Management.

Stripe should feel this

Stripe has offered billing natively for years through Stripe Billing, and it has been a real advantage in enterprise and SaaS deals. Enterprise merchants increasingly choose processors partly on billing capability. With Orb, Adyen closes one of the clearest gaps between the two. For a broader comparison, see Adyen vs Stripe: An Enterprise PM’s Honest Comparison.

What Merchants Should Consider

• Bundling versus best of breed. A unified platform simplifies reconciliation and retry logic, but concentrates vendor risk.
• Data ownership. Make sure usage data and invoices can be exported if you ever change providers.
• Authorization reporting. Ask for approval rates segmented by invoice size and billing cycle, not just overall.
• Integration roadmap. Acquisitions take time to integrate. Ask what works together today versus what is planned.

My Read

Adyen is no longer only a payment processor. It is building unified revenue infrastructure: metering, billing, authorization, settlement and reconciliation in one platform. The enterprise revenue infrastructure race is now a real contest.

Who wins it: Adyen, Stripe or someone else?

Source: Adyen press release, 11 June 2026.

FAQ

What is Orb?

Orb is an enterprise billing platform built for usage-based and consumption pricing, where customers are billed by units such as API calls, tokens or outcomes rather than by fixed seats or subscriptions.

How much did Adyen pay for Orb?

Adyen announced a definitive agreement on 11 June 2026 to acquire Orb for $335M. It followed Adyen’s acquisition of Talon.One earlier in the year, its first acquisition in 20 years.

Why does billing matter for authorization?

With usage-based pricing the amount charged changes every cycle. Retry logic, dunning and authorization optimization have to work with the billing engine, because a failed payment on a variable invoice is handled differently from a fixed subscription charge.

A shorter version of this analysis was first published on LinkedIn on June 13, 2026.

Related Reading

• Subscription Payment Retry Logic and Dunning Management: A Payments PM’s Guide
• Adyen vs Stripe: An Enterprise PM’s Honest Comparison
• Authorization Rate Optimization: A Payments PM’s Complete Guide
• What Is Payment Orchestration? Definition, Benefits, and Examples