TL;DR
- On June 11, 2026, Adyen agreed to acquire enterprise billing platform Orb for $335 million. The deal closes July 1, 2026.
- Adyen’s long-term goal is to converge billing and payments into a single platform. For subscription merchants, this continues a pattern of PSPs expanding into adjacent stack layers.
- The structural hedge is a routing architecture that stays independent of any single PSP’s roadmap: multi-provider routing with local acquiring in each market, operating regardless of which vendor runs the billing engine.
Context
Adyen N.V. announced on June 11, 2026 that it has agreed to acquire Orb, an enterprise billing platform, for $335 million in an all-cash deal. The acquisition closes July 1, 2026, alongside Adyen’s previously announced acquisition of loyalty platform Talon.One.
Orb provides billing infrastructure for complex pricing models. It ingests real-time usage events at scale and translates them into invoices, making it suited to usage-based pricing (UBP) models, where a customer’s bill varies based on API calls, compute time, seats activated, or similar consumption metrics. Orb’s current customers include AI-native businesses that shifted from fixed subscription pricing to metered models: Vercel, Glean, Replit, and Supabase.
Adyen’s rationale centers on the shift toward usage-based monetization. According to Adyen, 85% of companies using subscription or seat-based pricing are now layering usage-based components on top. Processing these models is more demanding than flat-rate subscriptions: a usage event stream must be captured, aggregated, rated, and invoiced before the payment authorization flow even begins.
Adyen’s stated long-term goal is to bring billing and payments together under one platform. During the first phase, it plans to run Orb under an incubator model, preserving its multi-PSP support. Beyond that first phase, the direction is convergence.
Analysis
This acquisition is the latest move in a consolidation pattern subscription billing teams should track. Payment service providers (PSPs) are systematically expanding into adjacent revenue layers: invoicing, billing, pricing, loyalty, and analytics. The commercial logic is straightforward for the PSP: owning more of the stack makes the relationship stickier and the contract larger.
For merchants using Adyen (or evaluating it), the near-term picture is stable. Adyen committed to maintaining multi-PSP support for Orb customers during the transition period. The medium and long-term question is harder. When billing logic and payment processing run on the same vendor’s roadmap, migration becomes more complex. Two systems that were once negotiated separately start to share pricing, support, and technical dependencies.
Usage-based billing raises the stakes further. Unlike flat-rate subscriptions, UBP models require the billing engine to process high volumes of usage events before the authorization attempt forms. If that event pipeline runs through the PSP’s infrastructure, switching the PSP means also migrating the event pipeline, the pricing logic, and potentially the invoicing history. That is a materially higher switching cost than swapping a payment integration.
For subscription billing teams, two implications stand out.
First, authorization rate optimization depends on routing flexibility. A subscription merchant with a multi-PSP stack can route each renewal attempt to the provider most likely to approve it, based on BIN (Bank Identification Number, the first 6-8 digits that identify the issuing bank and country), card type, market, and current network performance. A French cardholder’s Visa renewal routes differently from an Australian cardholder’s Mastercard attempt. That routing flexibility only works when the merchant can move authorization traffic across providers.
Second, local acquiring depends on infrastructure independence. Processing transactions locally in each market, rather than cross-border, requires maintaining acquiring relationships in multiple jurisdictions. A French card authorized through a French acquirer is a local transaction from the scheme’s perspective: lower scheme fees, higher issuer approval rates. That local classification only works if the routing layer can direct each transaction to the right acquirer independently of the billing engine.
How SGW absorbs this
The Adyen-Orb convergence surfaces a structural question every subscription billing team will face as PSPs expand their scope: is the routing layer in your stack genuinely movable, or is it entangled with your billing vendor?
SGW Payment addresses this from the routing side. Through a single SDK and API, SGW connects merchants to a network of payment providers and routes each transaction to the provider most likely to approve it. The routing layer sits above any individual PSP, which means authorization traffic can move based on performance, cost, and approval rate without triggering a billing migration.
On the infrastructure side, SGW stands up the local payments setup in each new market on the merchant’s behalf: entity incorporation, banking and acquiring relationships, PSP contract negotiation, and downstream finance operations including reconciliation, cash flow, and local tax clearance. Each market processes transactions locally rather than cross-border. The combination of local acquiring and multi-provider routing lifts approval rates significantly and compounds across the merchant’s full international footprint.
Setting up local processing in a new market independently takes 6 to 12 months. SGW runs the full process, so the merchant gains local processing coverage in each geography without building a local team or navigating the regulatory, banking, and tax landscape independently.
The practical implication: design the routing and local-processing layer to be durable against any single PSP vendor’s acquisition strategy. The billing engine can change; the routing layer should not depend on it.
Takeaways
- Adyen’s $335 million acquisition of Orb (closing July 1, 2026) signals that PSPs are moving to own the billing layer, not just the payment processing layer.
- For subscription merchants on converged platforms, switching cost rises: migrating a PSP that also handles billing logic is more complex than migrating a payment integration alone.
- Routing flexibility depends on keeping authorization traffic movable across providers. That option narrows when the billing engine and the PSP share a vendor roadmap.
- Usage-based billing raises the stakes: an event pipeline integrated with the PSP means the PSP holds the data that determines what customers owe before a transaction is even formed.
- The structural hedge is a routing architecture that operates independently of any single PSP: multi-provider routing, with local acquiring in each market.
- For subscription businesses expanding into new geographies, setting up local acquiring independently takes 6 to 12 months per market. Working with an infrastructure layer that already has local setup in place converts that timeline and preserves routing optionality simultaneously.
Sources
- Adyen to acquire Orb to unify billing and payments infrastructure for enterprise merchants — Adyen
- Adyen to acquire billing platform Orb for USD 335 million — The Paypers
- Adyen to buy Orb for $335M — Payments Dive
- Adyen signs all-cash deal to acquire Orb for $335m — FinTech Futures
- Adyen aims to tackle complex AI pricing with Orb acquisition — PYMNTS
- Orb joins Adyen to unify revenue design — Menlo Ventures
About SGW Payment — SGW Payment helps online businesses capture more revenue and reduce processing costs. Through a single SDK and API, SGW connects merchants to a network of payment providers and routes each transaction to the provider most likely to approve it. On top of the technology, SGW acts as the payments infrastructure layer for international expansion, standing up the local payments stack (entity, banking, acquiring, and finance operations) in every new market, so transactions process locally rather than cross-border. Learn more at sgw-payment.com.
