Stripe agreed to acquire Rungate for $310 million in cash and stock, both companies confirmed Thursday. Rungate, founded in Dublin in 2021 and later headquartered in New York, sells payment orchestration: software that sits above multiple payment processors and routes each transaction to whichever is most likely to approve it, with automatic retry through an alternate provider on decline. Its customer list includes three large European travel companies and a US subscription business processing above $2 billion annually. The strategic read is unusual, because orchestration exists specifically to reduce a merchant's dependence on any one processor, and Stripe is the processor most merchants are trying to avoid depending on.
What orchestration does
Card authorization is not deterministic. The same transaction submitted through two different acquirers can produce an approval and a decline, because issuing banks weight the acquirer's identity, the message format, the network token status, and a dozen other signals in their fraud models. Merchants processing at scale discovered that routing decisions move authorization rates by 1 to 3 percentage points, which on a billion dollars of volume is worth eight figures of recovered revenue annually.
Rungate's product models those differences and routes accordingly, learning per issuer, per card type, per geography, and per transaction size. It also handles the retry logic that turns a soft decline into an approval on a second attempt through a different path, subject to network rules about retry frequency. Customers report authorization improvements between 0.8 and 2.4 percentage points, and the company charges a per-transaction fee plus a share of recovered revenue.
Why Stripe wants it
The charitable explanation is that Stripe wants the routing intelligence for its own network, applying Rungate's models to decisions Stripe already makes internally about which acquirer and which network token to use. Stripe has invested heavily in authorization rate optimization and markets it as a differentiator, and buying a team that has been solving the problem across processors gives it comparative data it could not otherwise obtain.
The less charitable explanation is defensive. Orchestration layers commoditize processors. If a merchant runs Rungate above Stripe, Adyen, and Checkout.com, switching providers becomes a configuration change rather than an integration project, and pricing negotiations shift toward the merchant. Every processor has watched orchestration grow with discomfort. Buying a leading one and controlling its roadmap is a rational response, and it is the response that regulators occasionally examine.
The story is rarely the launch. It is what breaks, what ships, and who owns the mess at 2 a.m.
What happens to Rungate's customers
Stripe says the product continues, that multi-processor routing including to competitors remains supported, and that existing contracts will be honored. Chief executive of Rungate, Siobhan Doyle, will lead a payments optimization group inside Stripe. Two Rungate customers we contacted said they had been told the same and both said they are evaluating alternatives anyway, because a routing layer owned by one of the destinations it routes to has an obvious conflict.
That skepticism is the acquisition's main risk. Orchestration's value proposition rests on neutrality, and buying the neutral party damages the asset. Competitors moved immediately: Primer, Gr4vy, and Spreedly all published comparison pages within a day, and at least one has been offering migration credits. The customers most likely to leave are the largest ones, which are also the ones whose data makes the routing models good.
The consolidation pattern
This is the fourth payments infrastructure acquisition above $200 million in eighteen months. Adyen bought a fraud modeling company in early 2026. Visa acquired a tokenization vendor. PayPal picked up a checkout optimization team. The pattern is large processors absorbing the layers that sit adjacent to them, which is what mature infrastructure markets do and which steadily reduces the number of independent companies a merchant can choose among.
Antitrust review is unlikely to block this one. Rungate's revenue, estimated at $28 million annually, sits below thresholds that trigger mandatory notification in most jurisdictions, and orchestration is a small market by revenue even if it is strategically important. The European Commission's ongoing interest in payments concentration means the deal will probably get a look, and probably clear.
What this means for merchants
The practical advice from payments consultants is unchanged and now more urgent: maintain at least two processor integrations regardless of whether you use an orchestration layer, and make sure your engineering team knows how to fail over. Companies that let a single integration atrophy discover during an outage or a pricing negotiation that they have no negotiating position and no alternative.
For merchants below roughly $100 million in annual volume, orchestration has never clearly paid for itself, and this acquisition does not change that. The complexity cost of running multiple processors exceeds the authorization gain until volume is large. Above that threshold the calculation flips sharply, and those merchants now have one fewer independent vendor to choose from and a reason to look harder at the remaining ones.
There is a quieter operational point that payments teams raised repeatedly this week. Orchestration layers accumulate institutional knowledge about which issuers decline which transactions and why, and that knowledge is worth more than the routing software. A merchant that outsources the entire decision loses the ability to reason about its own authorization rates, which is fine until a rate drops and nobody internally can explain it. The teams that get the most from these tools treat the vendor as a source of data they analyze themselves rather than as a system that quietly optimizes on their behalf, and they keep at least one analyst who understands the underlying network economics.
Skarvonix will keep following this beat with reporting grounded in how systems behave outside the launch keynote.
- Funding
