Payments Margin Is a KPI Nobody Owns

I have sat in on a lot of conversations with vertical SaaS platforms about their payments business, and almost all of them start the same way. Payments began as a feature. Product owned it, because that is where features live, not because anyone was thinking about it as a monetization line yet.

That is not where the story ends, and this is the part I think most people miss. As a platform grows, payments do not stay with Product. Implementation picks up a piece of it, because customers are onboarding and need help getting set up. Support picks up another piece, because payments become more central to the product and customers start asking harder questions. Finance ends up with a piece too, because someone has to report the number every month.

None of that is wrong, exactly. Every one of those pieces genuinely needs an owner, and in most companies I talk to, it has one. The problem is what happens between the pieces. Nobody is holding the full payments journey: attach rate, adoption, how take rate evolves over time, whether interchange is optimized. Everyone owns a slice. Nobody owns the whole thing.

The number has an owner. The KPIs behind it do not.

Here is the distinction I think gets flattened whenever people talk about payments margin as something “nobody owns.” It is not accurate to say nobody owns it. The CFO almost always owns the number. They report it monthly, alongside every other line on the P&L, and they can tell you whether margin moved up or down since last quarter.

What the CFO usually cannot tell you is why. That is because the things that actually move payments margin sit with the departments I just described. The CFO sees the number every month, but the KPIs that influence that number are owned by everyone but no one.

That gap is not a staffing failure. It is a structural one. Nobody sat down and decided that attach rate would live in Product, adoption would live in Implementation, and take rate optimization would live nowhere in particular. It happened because payments grew up as a feature first, and features get organized around the product roadmap, not around a P&L line.

What that gap actually costs you

The cost is not that margin silently disappears while nobody notices, though that can happen too. The more common cost is that you end up reacting instead of operating strategically. Payments is already a complicated business on its own terms. If you do not have a payments expert on the team, and you do not have anyone holding the full KPI view, you are going to miss money. Not because anyone is careless, but because nobody has the vantage point to see the pattern until it has already cost you something.

I have seen a few specific versions of this play out.

One platform we talked to had a consultant on retainer for exactly this kind of work. The consultant was genuinely good at the diagnostic side: they would come back with a clear list of what was wrong. What they did not do was help fix any of it. Diagnosis without follow-through is its own kind of ownership gap. Someone found the problem. Nobody was positioned to act on it.

Another platform we spoke with was mid-negotiation, trying to move off a blended-rate agreement onto an interchange-plus model. Their processor has the underlying cost data. They asked for it directly. The processor said no, and offered an average instead. That platform is negotiating its own contract without the numbers it needs to negotiate well, not because the data does not exist, but because the party holding it has no incentive to share it.

A third example is the one that surprised me most, because on paper this company had solved the ownership problem. One person there described themselves, unprompted, as the end-to-end owner of payments. That is exactly the setup you would want. And that same person still could not explain why margin was dropping on one specific card category. The network was not saying why. The processor did not know either. Having a named owner did not give that owner visibility into the mechanics driving the number. The title existed. The KPI view still did not.

Why the standard advice is not wrong, just incomplete

If you search for how to fix this, you will find three answers, more or less. Lean on your processor. Hire a Head of Payments. Bring in a consultant. All three are legitimate, and I do not think any of them is bad advice. I think each one is a partial answer that gets sold as a complete one.

Your processor is a genuine payments expert. They are not an expert on your platform, your merchant mix, or your product roadmap, and you cannot treat them as a neutral party in a conversation about what you are being charged. The example above, where a processor had the data and chose not to share it, is not an edge case. It is what happens when the only party with full visibility also has a financial interest in you not having it.

A Head of Payments is, in most cases, exactly the right hire. The problem is timing. That role requires a real investment, and most companies are not in a position to make it until they hit a certain scale. From what I have seen across a lot of these conversations, the shift usually happens somewhere around $800 million in processing volume, or once a CFO recognizes that payments has grown to represent 30 percent or more of revenue. Before that point, most companies genuinely cannot justify the hire. That does not mean the ownership gap does not matter before then. It means the shape of the solution has to be different.

Scale does not solve this on its own, either. There are many platforms doing close to a billion dollars a year that still runs payments through its CFO, with no dedicated team in place. Crossing a revenue threshold creates the opportunity to formalize ownership. It does not create the ownership by itself. Someone still has to decide to make the change.

A consultant solves a specific, bounded problem well. What a consultant is structurally not able to do is stay integrated into your business the way an internal function would. They show up, find something, and leave. The finding is real. The follow-through is usually still missing, which is the exact gap in the retainer example above.

What actually needs to be true, regardless of your size

I do not think the answer is that smaller platforms should wait until they can afford a full-time Head of Payments before anyone owns this. A company that cannot yet justify that hire still needs a named owner. It does not have to be someone’s whole job. It has to be someone’s job.

What that means in practice is less about hiring and more about assignment. Someone, at any size, should hold the full KPI view: attach, adoption, take rate over time, interchange optimization, watched together rather than scattered across whichever team happened to inherit each piece. That is a different bar than “we have a payments person now.” It is closer to “one person can answer questions about the whole journey, not just their corner of it.”

This is also the gap payment margin leakage tends to live in. Leakage is usually not caused by one dramatic failure. It accumulates in the space between departments that each own a fragment and nobody who owns the seams. The same is true of processor contract drift: a contract quietly stops matching what you are actually being charged, and it takes someone watching the full picture to catch it before it compounds. Once you are looking closely enough to catch that, the same discipline tends to surface interchange downgrades too, since both problems hide in the same blind spot.

Payments margin ownership FAQ

What does it mean to “own” payment margin as a KPI? It means one person can account for the full picture behind the number, not just report it. That includes attach rate, adoption, how take rate changes over time, and whether interchange is optimized, tracked together rather than split across whichever department happens to touch each piece.

Is it true that nobody owns payment margin? Not exactly. The number itself is almost always owned, usually by the CFO, who reports it monthly. What is missing is ownership of the KPIs that move that number, which tend to be split across Product, Implementation, and Support as payments grows from a feature into a core part of the business.

Do we need a full-time Head of Payments to fix this? Eventually, probably. Based on what we have seen across a range of platforms, dedicated payments hires tend to appear once a company crosses roughly 800 million dollars in processing volume, or once payments reaches about 30 percent of revenue. Before that point, the ownership gap still needs to be closed. It just needs a named owner as part of a broader role, not a new full-time hire.

Does hitting that scale threshold fix the problem automatically? No. We know of platforms processing close to a billion dollars a year that still run payments through the CFO with no dedicated owner. Scale creates the opportunity to formalize ownership. It does not create the ownership on its own.

Can our processor or a consultant just handle this for us? Partially, and each has a real limit. A processor understands payments broadly but is not a neutral party and is not an expert on your specific platform. A consultant can diagnose a specific problem well but is not positioned to stay integrated with your business the way an internal owner would be. Both are useful. Neither replaces having someone who holds the full picture continuously.

Find out who owns this at your company

If you are not sure anyone on your team could answer questions about attach rate, adoption, take rate evolution, and interchange optimization all at once, that is worth finding out before it costs you more than it already has. If you want to see what that full picture looks like for your own payments business, get in touch about a demo and we will show you what we find.