Payments M&A: The Revenue Multiple Is the Easy Part
A payments acquisition can look attractive on revenue and still hide concentration, compliance, technology, and sponsor-bank risks. Good diligence follows the transaction flow—not just the financial statements.
Payments Revenue Is Not All the Same
Payments businesses often look appealing in an acquisition model. Transaction revenue is recurring, customer relationships can be sticky, and scale can improve processing economics. A portfolio of merchant residuals or program-management fees can resemble an annuity.
But the quality of that revenue depends on infrastructure and relationships that may not appear clearly in the financial statements.
A payment company can own customer contracts while depending on a processor, sponsor bank, card network, gateway, or critical software platform to deliver the service. If one of those relationships changes, the economics can change immediately.
Follow the Transaction
Effective diligence starts by mapping how a transaction moves from the customer to authorization, clearing, settlement, reporting, and exception handling. At each step, the buyer should identify who performs the work, who owns the contract, who bears the risk, and what happens if the relationship ends.
This exercise often reveals dependencies hidden by simple labels such as "processing expense" or "bank partner." A favorable processing rate may depend on a volume commitment that becomes unrealistic after a customer loss. A sponsor-bank agreement may permit termination with limited notice. A proprietary platform may rely on a small team with undocumented knowledge.
Understanding the transaction flow also exposes which capabilities are genuinely owned by the target and which are rented from third parties.
Concentration Has Several Forms
Customer concentration is the obvious risk, but payments companies can also have processor concentration, sponsor-bank concentration, vertical concentration, and referral-partner concentration.
Revenue spread across thousands of merchants may look diversified until diligence shows that most merchants arrived through one software partner. A program with several bank relationships may still rely on one institution for its highest-margin product.
Concentration is not automatically disqualifying. It needs to be priced, protected contractually where possible, and included in integration planning.
Compliance Quality Affects Value
Payments compliance is not only a risk-control question; it is a valuation question. Weak merchant underwriting, inconsistent complaint handling, incomplete monitoring, or informal oversight can require expensive remediation after closing.
Buyers should examine actual files and operating evidence rather than relying only on policies. Are high-risk merchants reviewed as the policy requires? Are alerts resolved with documented reasoning? Are sponsor-bank findings tracked to closure? Do network registrations and licenses match the activity being conducted?
The answer influences both purchase price and the resources required after closing.
Integration Can Destroy the Asset
The value of many payments acquisitions sits in customer retention and operational continuity. An aggressive platform migration, pricing change, or support reorganization can damage both.
Integration planning should therefore begin during diligence. Which systems must remain temporarily? Which customer contracts require consent? Will tokens or stored payment credentials survive a processor migration? Which employees hold essential partner relationships?
The headline multiple may determine whether a deal enters the pipeline. The durability of revenue, contracts, compliance, and infrastructure determines whether the deal creates value. In payments M&A, the most important diligence questions are usually found beneath the transaction—not at the top of the income statement.