
From Model Governance to Machine Agency: Governing AI that Acts, Not Just Answers
Learn how to govern Agentic AI with human oversight, delegated authority, runtime controls, and accountability to enable secure, responsible enterprise AI.
Merchant acquiring crossed a threshold in January 2026, when Global Payments completed its $24.25 billion acquisition of Worldpay. The combined company now serves more than 6 million merchant locations, processing $3.7 trillion in payment volume and approximately 94 billion transactions annually across more than 175 countries. That is scale on paper. Scale in production gets decided later, inside the platform integration, where merchants either keep transacting or quietly leave. This is what it takes to merge acquiring platforms without losing a single merchant.
The morning after a merger closes, the combined company owns several of everything. Multiple gateways and checkout flows. Separate POS and mPOS estates. Parallel virtual terminals. Duplicate merchant onboarding processes, each with its own risk logic. Fraud controls that cannot see across the portfolio.
Global Payments has committed to approximately $600 million in annual run-rate expense synergies over the three years following close, alongside at least $200 million in revenue synergies, primarily by combining business operations and technology infrastructure. Those numbers get earned or lost in the migration, not in the announcement.
Merchants feel the integration before the market does, and their tolerance is thinner than most acquirers assume. Capgemini’s World Payments Report 2026, based on a survey of 2,600 merchants across 15 markets, found that 70% of merchants value high payment success rates and reliable infrastructure, while only 19% of banks feel confident they can deliver them. Sixty-nine percent of merchants want fast and seamless onboarding, against just 13% of banking executives who feel equipped to provide it. Merchants already lose up to nine hours a year to unreliable payment systems, and 40% of small and mid-sized merchants are weighing a shift to PayTechs. A migration that adds friction lands on top of all of that.
The acquirers that win consolidation treat the target platform as a product and the migration as an engineering program with merchant experience as its first requirement. Altimetrik’s payments engineering approach follows five moves, sequenced by what breaks first.
Reusable components, DevOps pipelines, and automated validation are what let one platform absorb four without the integration decaying into a multi-year rewrite.
Most integrations get structured as parallel workstreams, one per inherited system, with each legacy platform owner keeping their piece. That mirrors the org chart of the two companies that just merged, which is precisely the problem. It guarantees the seams survive the migration.
The layers are coupled. Checkout cannot move before the token vault behind it is ready. Onboarding decisions depend on the risk engine that scores them. Fraud rules need visibility across the combined portfolio before any cohort is cut over. Sequence one of those independently and the rest inherit a dependency nobody owns.
The correction is to change the unit of migration. Merchants do not experience gateways, vaults, and onboarding as separate systems, so the work should not be planned as though they do. Move merchant cohorts rather than platforms, and make every layer that cohort touches move with it. The programs that finish on schedule are the ones where sequence and ownership were settled early, not the ones with the best tooling.
Consolidation will keep reshaping merchant acquiring, and every deal will promise synergies. The acquirers that realize them will be the ones that integrate fastest and most invisibly, keeping every merchant transacting while four platforms quietly become one, and emerging with the omnichannel infrastructure merchants now expect. Treat integration as the deal thesis itself, and the market share the merger bought stays bought.
Facing a post-M&A platform integration? Explore Altimetrik’s payments engineering capabilities or talk to our team.
Najmi Surti, Head of Payments & Fintech Products at Altimetrik

Learn how to govern Agentic AI with human oversight, delegated authority, runtime controls, and accountability to enable secure, responsible enterprise AI.

Swift’s SR 2026 delay changes the ISO 20022 roadmap. Learn what banks need to do now on structured addresses, compliance, data quality and migration.

Code generation got fast. Getting an autonomous workflow into a bank’s production control environment did not. In Banking & Financial Services (BFS), the blocker is rarely the model; it’s trust. A risk officer will not sign off on a system that cannot say why it flagged something, that does its arithmetic inside a language model, or that leaves no audit trail an examiner can open. That is exactly the gap most agentic pilots die in.
Over the last two quarters, we built a portfolio of ten BFS agentic offerings on Alti AIOS™, Altimetrik’s AI Operating System, and deployed them on two stacks: Google Cloud with Gemini and AWS with OpenAI. This piece is the architecture and design principle behind them.
USA (Southfield) - HQ
2000 Town Center, Suite 170
Southfield, MI 48075
+1 248-281-2500