What Payments Unit Economics a Generalist Fractional CFO Will Not Already Know · Midcore Operations
Midcore Operations
Business Operations

What Payments Unit Economics a Generalist Fractional CFO Will Not Already Know

A payments company's gross revenue is not its margin. Its balance sheet also carries matched pairs that are not real assets or real debt.

Published
19 November 2026
Reading time
9 min read
Author
Business Operations practice
Topic
Business Operations
Key takeaways
  • A public payments company's own SEC filings confirm that processing revenue is reported gross, as a principal under ASC 606, of amounts paid to sponsor banks plus interchange and assessments paid to card associations. A generalist CFO reading reported revenue as a clean top-line signal is reading a number that is mostly pass-through with no margin in it at all.
  • Settlement processing assets and the matching settlement processing obligations on a payments company's balance sheet represent intermediary balances moving through the settlement process, not real economic assets or real debt. The same mirrored structure applies to prepaid card load assets and obligations.
  • Merchant reserves are carried on the balance sheet as both an asset and a corresponding liability, funds collected from each merchant and held as collateral against contingent chargeback and return liability, not working capital available to the business that holds them.
  • A generalist analyzing total assets, leverage, or working capital on a payments company's balance sheet without backing out these matched pairs is measuring the size of money moving through the business, not the size of the business itself.

What payments unit economics a generalist fractional CFO will not already know comes down to two specific things that look nothing like what a normal operating business’s financial statements show. Reported revenue in this industry is typically gross of amounts that never become margin at all. And the balance sheet carries large, matched pairs of assets and obligations that represent money moving through the business rather than money the business actually owns or owes. A CFO who has not worked inside payments specifically will read both numbers at face value, and both readings will be wrong.

Why the top line is not what it looks like

A public payments company’s own audited financial statements describe exactly how this works, in language a generalist rarely encounters anywhere else. Usio, Inc.’s 2025 Form 10-K, filed with the SEC, states plainly that revenues from electronic processing of credit, debit, and prepaid card transactions are reported gross of amounts paid to sponsor banks. Interchange and assessments paid to credit card associations are included too. The filing is specific about the accounting basis behind this. The company complies with ASC 606-10 and reports revenue at gross as a principal rather than net as an agent, having determined for each processing agreement that it is acting in the principal role.

What this means in plain terms is that the reported revenue figure includes money the company never keeps. Interchange, the fee that flows to the card-issuing bank, passes straight through the reported top line. So do the assessments owed to the card networks themselves. A generalist CFO looking at a payments company’s revenue the way they would look at a SaaS company’s revenue is comparing two numbers built on completely different logic. A software company’s revenue is close to what it keeps. A payments company’s revenue, reported this way, mostly is not.

Why this distorts every ratio built on revenue

This matters well beyond how a single number reads on a page. Growth rate, revenue multiples, and margin percentages are all built on top of this top-line figure. Every one of them inherits the distortion. A payments business growing its gross processing volume by signing larger merchants can show impressive revenue growth. Most of that growth can reflect a shift in who is sending pass-through dollars through the business, not a real change in what the business earns. A generalist CFO benchmarking this company against a software peer group on a revenue multiple is benchmarking against a fundamentally different kind of number without realizing it.

The fix is not complicated once it is understood, but it has to actually be applied. Net revenue is the amount left after interchange, assessments, and sponsor bank fees come out. That number behaves the way a generalist expects revenue to behave elsewhere, closer to what the business actually captures, and a far more honest base for a multiple, a growth rate, or a margin calculation. The gross figure still matters for understanding volume and market position. It is simply the wrong number to run unit economics on.

The balance sheet pairs that are not what they look like either

The same filing describes a second pattern that is just as easy for a generalist to misread. Settlement processing assets and settlement processing obligations represent intermediary balances arising in the settlement process for merchants. In plain terms, these are funds in transit at a given moment between the merchant, the processor, and the card networks. They appear on the balance sheet as a matched pair, an asset of a given size and an equal offsetting obligation, because the company is temporarily holding money that belongs, in substance, to someone else in the chain. The same structure applies to prepaid card load assets and obligations. The filing describes these as pre-funding accounts maintained to facilitate prepaid card loads, carried with a corresponding liability of the same size.

A generalist CFO reading a balance sheet with large settlement processing assets has two very different ways to interpret that number. One interpretation treats it as real, deployable capital, the way accounts receivable or cash on hand would normally be treated. The correct interpretation recognizes that the matching obligation sitting right next to it cancels out most of what the asset alone would suggest. Total assets and total liabilities both grow by the same amount when settlement volume grows. A business processing more volume can show a dramatically larger balance sheet without becoming a dramatically larger company in any sense that matters for solvency or leverage analysis.

What merchant reserves actually are, and what they are not

A third item requires its own explanation, because it is easy to mistake for ordinary working capital. The same filing describes merchant reserve requirements associated with transaction processing. Merchant reserve assets are carried on the balance sheet with a corresponding liability. Funds are collected from each merchant and held specifically as collateral. That collateral minimizes the contingent liabilities tied to that merchant’s processing activity: chargebacks and returns the company might otherwise have to absorb if the merchant cannot or will not cover them.

This is money the company is holding on behalf of a specific future claim, not money it can spend running the business. A generalist CFO assembling a working capital analysis without separating merchant reserves from genuinely available cash is overstating the company’s actual liquidity. How much depends on how large the reserved merchant portfolio is relative to the company’s overall size. The reserve exists because the company’s own risk exposure requires it, not because the business happens to be holding extra cash it has not yet deployed.

Why this connects back to the merchant discount fee itself

Visa’s own rules describe the structural reason this gross-versus-net distinction exists in the first place. The interchange reimbursement fee is a default transfer price between the card-issuing bank and the acquirer. That is separate entirely from the merchant discount fee the acquirer actually negotiates with the merchant, which factors in that interchange cost alongside processing costs and other services. A payments company sits on the acquiring side of exactly this structure. The money flowing through it as reported revenue includes that default transfer price on its way to the issuing bank. That is precisely why the top line and the actual economic capture are two different numbers by design, not by any accounting choice unique to one company.

This structural split also explains why two payments companies with identical reported revenue can have completely different margins. One might acquire mostly low-ticket, low-interchange debit transactions where the pass-through is small relative to its own fee. The other might acquire mostly premium rewards credit cards where interchange eats a far larger share of every dollar before the acquirer’s own fee is even applied. Reported revenue treats both the same. Net revenue does not, because net revenue is the number that actually reflects which of the two businesses captures more value per dollar processed.

A concrete example: the acquisition model built on the wrong number

Picture a generalist CFO evaluating a payments platform for a potential investment. The model is built off the target’s reported revenue growth, with a multiple pulled from a set of software company comparables. Reported revenue has grown thirty percent year over year, which looks like a strong signal on its own. What the model does not separate out is where that growth actually came from. Several large-ticket merchants were onboarded whose transaction volume, and therefore whose interchange and assessment pass-through, dwarfs the company’s actual fee income from them.

Net revenue for the same period grew closer to eight percent. The valuation built on the gross figure and a software-style multiple overstates the company’s actual worth by a wide margin, and a lender or acquirer’s own diligence team will catch the gap immediately by asking for net revenue instead. The CFO who built the model off the number that looked most familiar, rather than the number payments businesses actually run on, produced a conclusion that does not survive the first real diligence conversation.

What this means for bringing in the right financial leadership

None of this means a growing payments business needs a specialist for every financial decision. It means the specific unit economics questions, what the real net revenue is after pass-through costs, what the balance sheet actually represents once matched settlement and reserve pairs are backed out, and what that means for a valuation, a credit facility, or a board conversation, need someone who has actually seen this structure before, not someone applying a general framework built for a different kind of business.

Bringing that specific payments fluency into the financial leadership conversation, rather than discovering the gap during a fundraise or a sale process, is exactly the value behind Midcore’s fractional CFO work. Building the net revenue and margin model correctly from the start, rather than reverse-engineering it under deal pressure, is the discipline behind pricing and revenue modeling engagements. And because the residual and fee detail behind that net revenue number is exactly what a residual audit and reconciliation engagement verifies line by line, the two disciplines end up supporting the same underlying number from two different directions.

Frequently Asked Questions

Why does a payments company’s revenue look much larger than its actual margin?

Because processing revenue is typically reported gross under ASC 606, as the principal in the transaction, which includes the full amount paid by the merchant before amounts owed to sponsor banks and interchange and assessments owed to card associations are subtracted out. A public payments company’s own SEC filings describe this directly: revenue is reported gross of those pass-through amounts. A generalist comparing that revenue figure to a software company’s revenue, where the top line is much closer to actual margin, is comparing two numbers that mean fundamentally different things.

What are settlement processing assets and obligations on a payments company’s balance sheet?

Intermediary balances arising in the settlement process for merchants, money that is in transit between the merchant, the processor, and the card networks at a given moment in time. They appear as a matched pair, an asset and an equal offsetting obligation, because the processor is temporarily holding funds that belong, in substance, to someone else. A generalist treating the asset side as real, available capital without recognizing the matching obligation is misreading what the number actually represents.

Are merchant reserves money a payments company can actually use?

No, not freely. Merchant reserves are funds collected from merchants and held as collateral specifically to cover contingent chargeback and return liability tied to that merchant’s processing activity. They are carried on the balance sheet as both an asset and a corresponding liability precisely because the funds are not the company’s own working capital. They exist to protect the company against a specific future claim, not to fund operations.

Sources: Usio, Inc., Form 10-K for fiscal year 2025, filed with the U.S. Securities and Exchange Commission, and Visa Core Rules and Visa Product and Service Rules, Section 1.8.1.2.

Business Operations practiceMidcore Operations · 19 November 2026
All insights
Free consultation

Get your free Assess

Tell us what is happening. We reply within one business day with a US-based practice lead, not a salesperson.

  1. 01Within 1 business dayA US-based practice lead replies and books a 30 minute call.
  2. 02On the callWe map the problem, the volume, the partners, and the constraints.
  3. 03After the callYou get a written read of one to three pages, yours to keep.
  • Handled under NDA
  • Written, not a slide deck
  • No obligation to continue

No obligation. We will tell you if you do not need us.

Before you go

Take the written read with you

Every engagement opens with an Assess: a written read of what is happening, what it costs, and what to do about it. It is quoted on its own and you can stop after it.

+1 (786) 619-0152