Most platforms measure their embedded payments program with one number: revenue. It is the easiest metric to pull and the one the board asks about. It is also the least useful for steering, because revenue is a trailing indicator. It reflects decisions made months ago, and by the time a problem shows up in the revenue line, you have already spent two quarters compounding it.
The platforms that build durable payments businesses manage them the way they manage the rest of the software P&L: with a small set of leading indicators, targets for each and a monthly review. This is the framework we use with operators, whether the program launched last quarter or three years ago. Seven metrics, with benchmarks and the combinations that tell you what is actually going on.
If you only take one thing from this piece, make it this: track these monthly, set a target for each and review them together. The signal is in how they move relative to one another, not in any single number.
The seven payments KPIs every vertical SaaS platform should track are merchant activation rate, net take rate, payments revenue per merchant, gross payment volume growth, chargeback ratio, boarding completion rate and cost to serve. Revenue is a trailing indicator. These seven, reviewed monthly, tell you whether the program is healthy before the revenue line does.
1. Merchant Activation Rate
The single most important leading indicator, and the one most platforms underinvest in. A platform with 500 merchants and 30% activation is in a fundamentally different position than one with 70% activation on the same base, and the revenue line will not tell you which you are until much later. Activation tells you whether your onboarding, positioning and go-to-market are working before revenue does.
Track it monthly, broken out by cohort (when the merchant joined the platform) and by segment (size, sub-vertical, acquisition channel). The cohort view tells you whether activation is improving over time. The segment view tells you where to focus. When activation is the metric you most want to move, the levers live in a dedicated piece: the Merchant Activation Playbook walks the structural reasons merchants stall and the sequence for fixing each.
2. Net Take Rate
Your net take rate tells you how efficiently you monetize volume, and the range you should expect depends on how your platform makes money from payments. If it is declining, you have one of three problems: pricing (giving away too much margin to win merchants), mix (high-volume low-margin merchants growing faster than the rest) or cost (processor spread eating your net). Each has a different fix, so the first job is to figure out which one you have.
Track it monthly. If it moves more than 3 to 5 bps in a quarter without a deliberate pricing change, investigate. The benchmark ranges above reflect typical economics by model. See ISV Referral vs PayFac Lite for the trade-offs that determine which range your platform sits in.
3. Payments Revenue per Merchant
This tells you whether your average merchant generates enough payment revenue to justify the cost of supporting them. If per-merchant revenue is $40/month and per-merchant support cost is $35/month, you have a unit economics problem that more volume will not solve, it will scale the problem.
The fix is usually pricing (charging higher rates to small merchants) or segmentation (focusing activation effort on merchants above a minimum volume threshold). Watch this number alongside cost to serve, below, because the two together define your contribution margin per merchant.
4. Gross Payment Volume Growth
GPV growth comes from three sources: new merchant activation (more merchants processing), organic merchant growth (existing merchants growing their own business), and seasonality. Decompose it into those components every month. If new activation is slowing but organic growth is strong, the program is healthy and the go-to-market needs attention. If organic growth is flat, your merchants may be stagnating, which is a software problem wearing a payments costume.
5. Chargeback Ratio
Track this at the portfolio level and flag individual merchants who exceed 0.5%. A single high-chargeback merchant can drag your aggregate ratio into monitoring territory if their volume is large enough. Monitor weekly, not monthly. By the time a monthly report surfaces a problem merchant, they may have been accumulating disputes for three weeks. For the operational side of keeping this number down, see chargeback management for software platforms.
6. Boarding Completion Rate
This is the conversion rate of your onboarding funnel. Every merchant who starts boarding but does not finish is acquisition spend lost at the last mile. Track it by step to find where merchants abandon, then fix the friction. The most common drop-off points are document upload and bank verification, and both are usually fixable without engineering. The full teardown lives in merchant onboarding for embedded payments.
7. Cost to Serve
Operating costs include support time (proportional), compliance (amortized), chargeback losses, processor fees beyond interchange and integration maintenance. If cost to serve grows faster than revenue per merchant, you are scaling in the wrong direction. The usual culprit is support, merchants generating more tickets than planned, often because the product experience is not clear enough to self-serve. For the full cost stack by model, see what embedded payments actually cost to operate.
How to Read These Together
No single metric tells the full story. The power is in the combinations, because each pair isolates a different problem:
- High activation + low take rate = you are winning merchants but not monetizing them. Pricing or model issue.
- High take rate + low activation = strong economics on a small base. Go-to-market or onboarding problem.
- Growing GPV + declining revenue per merchant = you are adding small merchants that dilute per-merchant economics. Segmentation issue.
- High boarding completion + low activation = merchants board but never process. Product integration or value-proposition problem.
- Flat chargebacks + rising cost to serve = the cost is in support and operations, not risk. Look at the product experience, not the underwriting.
How Often to Review, and With Whom
Cadence matters as much as the metrics. Chargeback ratio is weekly, because the cost of a late catch is real money and monitoring exposure. The other six are monthly, in a standing review that includes product, not just finance, because most of the fixes (onboarding friction, activation, support load) are product decisions. Quarterly, pull the cohort view and ask whether each new cohort is activating faster than the last. If it is not, your go-to-market is not learning.
The single biggest process failure we see is payments getting reviewed in the finance meeting as a revenue line and nowhere else. A program managed that way drifts, because the people who can move the leading indicators are never in the room.
The Metrics to Stop Watching
A few numbers get tracked because they are easy, not because they steer anything. Total transaction count tells you almost nothing on its own, volume and revenue already capture it. Gross payment volume without the activation and take-rate context is a vanity number, a platform can grow GPV while its economics quietly erode. And raw merchant count, divorced from activation, is the most misleading of all, it is the metric that lets a platform tell itself the program is working while 70 percent of the base has never processed a dollar.
The platforms that treat payments as a managed business line, with KPIs, targets and monthly reviews, outperform the ones that check revenue quarterly and assume it is working.
The Margin Multiplier gives you the revenue baseline. These KPIs tell you whether you are tracking toward it. And when an exit or fundraise is on the horizon, the same numbers show up in payments due diligence, so a platform that has been managing to them is also a platform that diligences well. For a working session on your own metrics and where the headroom is, see the advisory engagement.