Revenue Isn't the Whole Story, six payments program health KPIs with healthy and warning benchmarks

Most platforms launch embedded payments with a clear metric in mind: revenue. But revenue alone doesn't tell you whether the program is healthy, growing efficiently, or worth continued investment. It's a trailing indicator of decisions made months ago.

The platforms that build durable payments businesses track seven metrics that, together, give a complete picture of program health. Here's the framework, with benchmarks for each.

1. Merchant Activation Rate

Activation Rate
Merchants processing ÷ Total eligible merchants
Benchmark: 30-40% year 1, 50-65% at maturity. Top quartile: 70%+

The single most important leading indicator. A platform with 500 merchants and 30% activation is in a fundamentally different position than one with 70% activation on the same base. This metric tells you whether your onboarding, positioning, and go-to-market are working, before revenue reflects it.

Track it monthly. Break it by cohort (when did the merchant join your platform) and by segment (merchant size, vertical sub-segment, acquisition channel). The cohort view tells you whether activation is improving over time. The segment view tells you where to focus.

2. Net Take Rate

Net Take Rate
Net payments revenue ÷ Gross payment volume (expressed in basis points)
ISV Referral: 5-15 bps | PFaaS: 25-70 bps | Full PayFac: 50-100 bps

Your net take rate tells you how efficiently you're monetizing volume. If it's declining, you have either a pricing problem (giving away too much margin to win merchants), a mix problem (high-volume low-margin merchants growing faster than others), or a cost problem (processor spread eating into your net).

Track monthly. If it moves more than 3-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

Revenue per Merchant
Net payments revenue ÷ Active processing merchants
Healthy range: $50-$300/month depending on vertical and model

This tells you whether your average merchant generates enough payment revenue to justify the cost of supporting them. If your per-merchant revenue is $40/month and your per-merchant support cost is $35/month, you have a unit economics problem that more volume won't solve.

The fix is usually pricing (charging higher rates to small merchants) or segmentation (focusing activation efforts on merchants above a minimum volume threshold).

4. Gross Payment Volume Growth

GMV Growth
Month-over-month or quarter-over-quarter change in gross payment volume
Healthy: 3-8% MoM growth in first 2 years. Adjust for seasonality in your vertical.

GMV growth comes from three sources: new merchant activation (more merchants processing), organic merchant growth (existing merchants growing their business), and seasonal effects. Decompose growth into these components monthly. If new activation is slowing but organic growth is strong, your program is healthy but your go-to-market needs attention. If organic growth is flat, your merchants may be stagnating, which is a software problem, not a payments problem.

5. Chargeback Ratio

Chargeback Ratio
Chargebacks filed ÷ Total transactions (monthly)
Healthy: <0.5%. Warning: 0.5-0.9%. Critical: >0.9% (Visa monitoring threshold)

Track at the portfolio level and flag individual merchants who exceed 0.5%. A single high-chargeback merchant can push your aggregate ratio into monitoring territory if their volume is significant. Monitor weekly, not monthly, by the time you see a monthly report, a problem merchant may have been accumulating chargebacks for three weeks.

6. Boarding Completion Rate

Boarding Completion
Merchants who completed boarding ÷ Merchants who started boarding
Self-serve: 35-55%. Staffed: 70-85%. Below 30% = UX problem worth fixing.

This is the conversion rate of your onboarding funnel. Every merchant who starts boarding but doesn't finish is revenue you've already spent marketing and sales effort to acquire, lost at the last mile. Track by step to identify where merchants abandon, then fix the friction points.

7. Cost to Serve

Cost to Serve
Total payments operating costs ÷ Active processing merchants
Should decline as program scales. Target: <30% of revenue per merchant.

Operating costs include support time (proportional), compliance (amortized), chargeback losses, processor fees beyond interchange, and integration maintenance. If cost to serve is growing faster than revenue per merchant, you're scaling in the wrong direction. The most common cause is support, merchants generating more tickets than anticipated, often because the product experience isn't clear enough to self-serve. For the full picture of what embedded payments actually cost to operate by model, the cost stack varies more than most teams expect.

How to Use These Together

No single metric tells the full story. The power is in combinations:

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's working.

The Margin Multiplier gives you the revenue baseline. These KPIs tell you whether you're tracking toward it. When an exit or fundraise is on the horizon, the same numbers show up in payments due diligence. For operational metrics review and optimization strategy, see the advisory engagement.