A merchant relationship can generate a processing residual. The more interesting question is what else that relationship gives you permission to solve.
On September 21, 2026, Priority Technology Holdings announced a definitive agreement to go private. An investor group led by Chairman and CEO Thomas Priore will pay $8.05 per share in cash for the shares it does not already own. Funds managed by Searchlight Capital Partners are providing part of the equity financing. The enterprise value is approximately $1.6 billion. The price is a 65% premium to the unaffected close on November 7, 2025, and a 38% premium to the close on September 18, 2026.
Against LTM Adjusted EBITDA of $235.3 million through June 30, 2026, that enterprise value is roughly 6.8x.
The easy way to file this deal is under merchant acquiring. That is the wrong drawer.
The Segment Mix Is the Story
Priority reports three segments. For the six months ended June 30, 2026, Merchant Solutions generated $337.6 million of revenue and $58.6 million of segment Adjusted EBITDA. Payables generated $62.9 million of revenue and $8.6 million of segment Adjusted EBITDA. Treasury Solutions generated $119.4 million of revenue and $94.2 million of segment Adjusted EBITDA.
These are segment measures, before centralized corporate costs. Add the three segment Adjusted EBITDA figures together and the total is higher than consolidated Adjusted EBITDA because Priority carries shared costs above the segment line. The 6.8x multiple is calculated on the consolidated figure, after those costs. Keep the two layers separate and the math stays honest.
Now look at the proportions.
Merchant Solutions was about 65% of segment revenue and about 36% of segment Adjusted EBITDA. Treasury Solutions was about 23% of segment revenue and about 58% of segment Adjusted EBITDA.
The smaller segment by revenue produced the majority of segment profit.
Treasury Solutions average account balances were $1.48 billion in Q2 2026. Total company account and deposit balances were $1.8 billion at June 30, 2026, up from $1.4 billion a year earlier. That is roughly 29% growth in balances in twelve months.
Priority does not publish a cohort-level bridge showing how many Merchant Solutions customers moved into Treasury Solutions products, and I am not going to pretend it does. Treasury Solutions also earns from balances, which makes part of its profit sensitive to balance levels and interest rates. If those balances leave or spreads compress, the economics compress with them.
That distinction matters. Priority’s segment mix does not prove merchant-level cross-sell. It proves that once a payments company earns the right to hold and help manage money, the profit pool can look completely different from acquiring. Credit to Tom Priore and the Priority team for building a portfolio whose own financials make that possibility visible.
The Residual Is the Entry Fee
The processing residual is real money, and it deserves respect. It pays the sales channel. It funds support. It proves that a merchant keeps running cards through you month after month, through rate changes, bank changes, and a steady stream of competitors knocking on the door with a lower quote. A residual book that holds up over years is evidence of a durable relationship.
The mistake is treating the residual as the ceiling on what that relationship is worth.
Acceptance is not the product. Acceptance is the permission.
Card processing gives you a useful but incomplete picture: transaction volume, seasonality, chargebacks, settlement timing, the deposit account, and often the software touching the transaction. It does not show cash balances, payroll pressure, supplier payments, or the full back office. That broader picture only appears when the merchant grants permission through bank, ledger, accounting, or payables integrations.
Then walk into the back office. The owner is reconciling deposits against a printed batch report taped to a clipboard. A part-time bookkeeper is matching three bank accounts in a spreadsheet on Sunday night. Supplier invoices get paid by paper check, signed by hand, and mailed with a stamp. When a slow month hits, the owner covers the gap with a personal credit card.
Every one of those is operating pain. Every one maps to a product: treasury and deposit accounts, banking services, lending, payables, reconciliation, and working capital. When an ISO has a durable, direct merchant relationship, it has earned the chance to ask for that next layer of permission. It has not earned the right to assume it.
The chain is straightforward. Acceptance creates the relationship and the data. Broader workflows deepen the economics and make the relationship much harder to replace. A merchant can switch processors to save a few basis points. Moving their operating account, their supplier payments, and their credit line all at once is a far bigger decision. That is why I have argued that treasury is retention infrastructure, not an add-on.
I learned the operating version of this at Finexio. We had four people working full time on supplier acceptance and onboarded 1,200 suppliers a month. We also had a dedicated retention role, and we captured the reason behind every supplier conversation. The adjacent economics did not appear because we added another product to a slide. They appeared because people, process, and data turned an existing payment relationship into a measurable service motion.
Merchant services works the same way. A residual book with weak partner ownership, dirty merchant records, and no direct permission is not a platform. It is a cash flow stream. The additional value exists only when the operator can convert trust into adoption at a servicing cost the new margin can support.
Not Every ISO Should Become a Bank
None of this means every ISO should apply for a charter or build a lending desk.
The wholesale ISOs I have looked at are small, lean businesses. They win because of the partners they support: the agents, sub-ISOs, and referral relationships that actually sit across the table from merchants. A shop with a few dozen employees cannot stand up bank sponsorship, a compliance program, a ledger, and a credit model for each new product. It should not try.
The practical model has three parts.
First, shared infrastructure. Compliance, banking relationships, ledger, and data platforms are built once and used across many ISOs, so no single network carries the full fixed cost.
Second, carefully selected products. Not every service belongs in every portfolio. A network heavy in restaurants needs different tools than one heavy in B2B distributors. The discipline is choosing the two or three products that fit the book and saying no to the rest.
Third, a better operating system behind trusted partner distribution. The partner keeps the relationship. The ISO keeps its brand and its people. What changes is the machinery behind them, which makes it cheap enough to deliver more than processing.
When the products fit and the servicing economics work, each party wins in a specific way. The merchant gets fewer vendors and less manual work. The partner earns more per merchant and has another reason to retain the relationship. The ISO adds margin without rebuilding every capability itself. The investor owns a relationship asset instead of only a residual stream.
Where AI Changes the Cost Curve
AI changes the cost curve on the manual work that has always made a merchant portfolio expensive to operate.
Take onboarding. Today a person reads bank statements, voided checks, and formation documents, types the fields into an application, and chases the merchant when something does not match. A model can extract those fields, compare them against each other, and flag the mismatch before an underwriter ever opens the file. The work shrinks from document chasing to exception review.
Take support. In payment support queues I have run, the same questions repeat: “where is my deposit” or “what is this line on my statement.” The answer already sits in processor data. AI can pull the batch, the settlement date, and the fee detail and draft the response, so a person approves it instead of researching it.
Take merchant data cleanup. Anyone who has inherited a residual book knows the same merchant appears under four spellings of the DBA, with the wrong MCC and a contact email that bounced two years ago. AI can propose duplicates, classifications, and reconciliations across processors, with a person clearing the exceptions. Clean, permissioned data is the precondition for everything else.
Take portfolio analysis. Declining volume, a change in settlement bank, a spike in chargebacks: each is an early signal that a merchant is about to leave or is in trouble. AI can watch every account every day and send the partner a short list worth calling.
Then take the part that matters most for the thesis: identifying the next useful product for each merchant. A merchant with a predictable seasonal cash gap is a working-capital conversation. A merchant cutting dozens of supplier checks a month is a payables conversation. A merchant sweeping balances to another bank is a treasury conversation. With the merchant’s permission, AI can turn processor and integrated financial data into a specific recommendation the partner can bring to that merchant.
When the partner already owns the relationship and the new product is simple enough to explain, that motion does not require a new salesforce. Complex treasury or credit products still need specialists. The economic test is the same: lower the cost of operating and selling the service below the margin it creates. That test only works if the cost and return of the AI work are measured workflow by workflow.
A Valuation Test for Investors
If you are underwriting a payments business, look past residuals and processing volume. Those numbers tell you what the relationship earns today. They do not tell you what it can support.
Ask five questions instead. First, partner durability: how long do the partners stay, and do they bring new merchants every year? Second, merchant access: does the business have direct, permissioned contact with the merchant, or does it sit three layers removed? Third, data quality: is the merchant data clean enough to act on, or is it a pile of mismatched records? Fourth, product permission: will this merchant trust this relationship with the next problem? Fifth, the cost of adding services: what does it cost, in people and systems, to deliver one more product to one more merchant?
A business that scores well on all five can be worth more than its residual book implies. One that fails the access, data, or servicing test should still be valued as a residual book. Priority’s segment mix shows how large the gap between those two outcomes can become.
Fern Capital’s thesis is to acquire wholesale ISOs with strong partner relationships and help those networks deliver more valuable financial services through shared technology and AI-enabled operations.
I will write more on this topic over the coming weeks, starting with how to measure partner durability and what a clean merchant data layer actually looks like inside a wholesale ISO.
The residual gets you in the door.
What is behind it is the real asset.
Sources
https://www.sec.gov/Archives/edgar/data/1653558/000121390026101651/ea030604701ex99-1.htm
https://www.sec.gov/Archives/edgar/data/1653558/000165355826000130/prth-20260630.htm
https://www.sec.gov/Archives/edgar/data/1653558/000165355826000127/ex991-prthq22026earningsre.htm