Payments Revenue at $100M Volume, comparing Year 1 and Year 3 net revenue across ISV Referral, Enhanced Residuals, PayFac-as-a-Service, and Full PayFac

Every vertical SaaS founder eventually asks the same question when they start looking at embedded payments: how much money is actually in this for us?

The honest answer is, it depends. The unhelpful answer is, a meaningful amount. The useful answer is, here are the specific numbers at the volume tiers most platforms operate in, and here is what swings them up or down.

The reason this question matters more than founders realize is that the numbers are large enough to materially change the trajectory of a vertical SaaS business, but they do not show up on the surface. The dollars are buried inside processor agreements, merchant pricing decisions, and operational choices that most founders never made deliberately. Until they get modeled, they are invisible.

For the structural overview of how each model generates revenue, see How SaaS Companies Make Money From Payments. This article is the financial version. Specific dollars at specific volumes, across all four embedded payments arrangements.

Why Volume Is the Single Biggest Variable

Most embedded payments revenue conversations focus on the model: should we be ISV Referral, PayFac-as-a-Service, Full PayFac? Those choices matter. But the variable that drives most of the revenue outcome is annual processing volume.

The reason is that all four models pay you a net basis point spread on the dollars flowing through your platform. A few extra basis points on $5M of volume is rounding error. The same spread on $200M is a meaningful business line. The model decision compounds with volume. Without volume, the model barely matters. With volume, it matters enormously. For the full breakdown of which model fits which volume tier, see Should You Become a Payment Facilitator?

The starting point for sizing your opportunity is understanding your current annual processing volume. If you do not know it, estimate it: average merchants times average monthly payment volume per merchant times twelve. Most platforms have this data buried inside their processor reporting and have never aggregated it.

What the Four Models Generate at Each Volume Tier

Here is the framework. Net economics by model, as published in What Is a Payment Facilitator?, applied across volume tiers most vertical SaaS platforms encounter. These ranges assume 60 to 75 percent merchant activation on payments, which is realistic for platforms past their first year of an embedded payments program. Year 1 results at lower activation rates would land at the lower end of each range.

$5M Annual Processing Volume

At this volume you are probably pre or early embedded payments. Revenue is modest in absolute terms but the operational simplicity matches the stage.

At $5M, ISV Referral is the right answer. Build the merchant volume first. The model upgrade comes later.

$25M Annual Processing Volume

This is the bottom of the meaningful zone. Revenue starts to be a real line item rather than a rounding-error residual.

The conversation at $25M is whether to move from ISV Referral to Enhanced Residuals or PFaaS. The math starts to work for the more sophisticated arrangement, but the operational lift needs to be priced in. The detailed comparison is in ISV Referral vs PayFac Lite.

$50M Annual Processing Volume

This is where embedded payments starts to become a strategic conversation rather than a residual.

At $50M, the right answer for most platforms is PFaaS. The mechanics of why are covered in detail in PayFac-as-a-Service.

$100M Annual Processing Volume

This is the inflection point. Payments revenue becomes a meaningful contributor to total revenue at this volume tier.

At $100M, the strategic question is whether PFaaS or Full PayFac. The marginal economics of going Full PayFac (typically 25 to 30 bps over PFaaS) start to clear the marginal operating cost (typically $300K to $500K per year), but barely. The decision tips on factors beyond pure economics, like the team's capacity for compliance load and the platform's strategic time horizon.

$200M Annual Processing Volume

At this scale, payments is a strategic business line. The model decision is no longer about whether to capture the economics; it is about which arrangement maximizes them.

$200M is where Full PayFac starts to feel like the right call rather than a stretch. The additional 25 to 30 bps of net spread is now generating $500K to $600K of incremental revenue, which clears the operating cost with margin to spare.

$500M Annual Processing Volume

At half a billion in processing volume, payments is a major revenue stream and the platform is in the territory where embedded payments materially influences enterprise valuation.

For the valuation impact of these revenue tiers, see Payments Revenue SaaS Valuation. At $500M of processing volume, payments alone is adding $30M to $60M of enterprise value at typical SaaS multiples.

Year 1 vs Year 3: The Compounding That Founders Miss

The numbers above are Year 1 estimates assuming 60 to 75 percent merchant activation. Year 3 numbers compound from two effects most platforms underestimate.

First, activation rates climb. Year 1 activation typically lands at 40 to 60 percent because the program is new, onboarding is unrefined, and merchant communication is still being optimized. By Year 3, well-run programs land at 70 to 85 percent activation. That difference alone is 40 to 60 percent more revenue at the same processing volume.

Second, attach rate per active merchant grows. Merchants who use payments early tend to expand usage as they grow. New revenue streams (additional payment types, recurring billing, ACH, terminal hardware) compound on top of the base.

Realistic Year 3 revenue, at the same platform volume but with mature activation and attach, runs 50 to 80 percent above Year 1 across all four models. That is why the strategic conversation about embedded payments has to look at the three-year picture rather than the launch year. The first-year revenue line is the floor of what the program produces.

This compounding is one of the things the Margin Multiplier can struggle to surface, because it operates on current volume snapshots rather than activation curves. Treat the calculator output as Year 1 directional and assume meaningful upside as the program matures.

What Swings the Numbers Up or Down

The ranges above are wide because vertical, merchant mix, and execution all swing the result by 30 to 50 percent in either direction. Four variables matter most.

Activation Rate

This is the single biggest swing factor. A platform with 80 percent merchant activation generates twice the revenue of an otherwise-identical platform with 40 percent activation. The activation playbook is its own discipline. For why most platforms underperform here, see Why Merchants Do Not Use Payments.

Vertical and Merchant Mix

Average processing volume per merchant varies by an order of magnitude across verticals. A platform serving high-ticket B2B services merchants ($100K+ annual processing each) generates very different economics from one serving low-volume retailers ($30K annual each). Take rate also varies by vertical because card mix, dispute rates, and chargeback exposure differ.

Processor and Provider Terms

The take rate ranges above assume reasonably negotiated arrangements. Poorly negotiated processor contracts (interchange-plus margins outside benchmark, fixed fees that compound, settlement timing penalties) can compress net economics by 30 to 50 percent. For the playbook on negotiating these terms, see How to Negotiate a Processor Agreement.

Pricing Strategy to Merchants

Whether you charge merchants effective rate, interchange-plus, or flat per-transaction pricing materially affects both net economics and merchant retention. Aggressive pricing maximizes take rate but reduces activation. Conservative pricing maximizes activation but caps take rate. The right answer is vertical-specific.

The Back-Book: The Biggest Hidden Lever in Year 1 Revenue

The activation conversation has two completely different shapes depending on which merchants you are talking about, and the financial impact of confusing them is large.

New-book merchants (onboarded after embedded payments launched) tend to activate at 70 to 85 percent in well-executed programs. The product surfaces payments during onboarding. The sales motion includes it from day one.

Back-book merchants (already on the platform before payments launched) typically activate at 15 to 30 percent in Year 1. They have an existing processor, an existing rate, an existing chargeback workflow they trust. The platform asking them to switch is asking them to take a real risk for a benefit they have not yet personally felt.

This matters financially because most platforms running embedded payments have far more back-book volume than new-book volume in their first 24 months. A platform with $100M of total processing volume might have $20M flowing through new-book merchants and $80M sitting in the back-book. The Year 1 net revenue impact at a 45 bps PFaaS take rate looks like this:

Same platform, same model, same volume. Three different outcomes, with a $144K Year 1 swing driven entirely by back-book conversion rate. This is why back-book activation is consistently the largest single revenue lever in the first 18 to 24 months of an embedded payments program, larger than picking the right model and larger than negotiating better processor terms.

Most platforms leave 60 to 80 percent of their back-book unconverted in Year 1. By Year 3 the gap compounds: unconverted back-book merchants renew with their existing processor on schedule and lock themselves in for another two to three years. The window for converting them closes quietly.

The platforms that actually convert back-book at scale share specific tactics. In-product rate comparisons that show merchants what they would have saved last month at the embedded rate. Support team enablement with handoff scripts and spiff structures so the team that already touches merchants becomes a conversion channel. Dedicated activation FTEs above $50M of installed-base volume, typically paying back in 4 to 8 months. Processor co-marketing programs that get negotiated into the processor agreement but almost never get volunteered (ask explicitly, and ask early). Renewal-window targeting that treats the 60 to 90 days before an existing processor contract renews as the highest-probability conversion window.

The operational playbook on each of these is its own discipline. A dedicated Margin Labs article on the back-book conversion playbook is in the pipeline. For the diagnostic on what holds back-book merchants in place before any of this matters, see Why Merchants Do Not Use Payments. For why even new-book activation underperforms, see Merchant Onboarding for Embedded Payments.

Why Most Platforms Underestimate Year 1

Founders running the math for the first time tend to make two mistakes that bias the Year 1 estimate downward by 30 to 50 percent.

The first mistake is using net merchant pricing rather than gross processed volume. The opportunity is on processed volume (the dollar amount running through the merchant's card swipes). Some founders accidentally model on the merchant's net revenue, which understates the base by 95 percent.

The second mistake is assuming current attach rate is realistic. Most platforms have legacy merchants who never adopted payments because the program did not exist or was poorly marketed when they onboarded. New merchants onboarded into a well-executed program activate at much higher rates. Modeling using your current installed-base activation rate dramatically understates what new cohorts will do.

For the metrics framework that catches these biases after launch, see Payments KPIs After Launch.

Two Ways to Use These Numbers

The numbers above are most useful for two specific conversations.

Building the internal business case. Founders pitching embedded payments to their board or finance team need a defensible Year 1 estimate and a credible three-year compounding story. The framework above gives you both. The structure is, at our current processing volume of $X, under PFaaS our Year 1 net revenue is $Y, scaling to $Z by Year 3 as activation matures. The Year 3 number is what justifies the upfront investment.

Framing the model decision. Founders deciding between ISV Referral, PFaaS, and Full PayFac need to see the dollar deltas at their specific volume tier rather than the bps deltas abstracted across all platforms. The same 25 bps spread is a $25K decision at $10M volume and a $1.25M decision at $500M. The numbers above let you frame the decision at your actual scale.

A Quick Gut-Check Calculation

If you take nothing else from this article, do this back-of-envelope math for your platform tonight.

  1. Estimate your current annual processing volume. (Merchants × average monthly volume × 12.)
  2. Pick the model you are operating under today (ISV Referral, Enhanced Residuals, PFaaS, Full PayFac).
  3. Multiply your volume by the midpoint of the bps range for that model (10 bps for ISV Referral, 22 bps for Enhanced, 45 bps for PFaaS, 80 bps for Full PayFac).
  4. Compare to what you are actually earning on payments today.

If your actual is meaningfully below the framework estimate, the gap is either activation, contract terms, or pricing strategy. All three are recoverable. The size of the gap tells you how big the recovery opportunity is.

If your actual is in line with the framework, the question shifts to model upgrade. Moving from your current model to the next tier up captures the bps delta on your existing volume, with implementation cost as the only meaningful drag. For the full framework on whether to make that move, the decision tree is in Should You Become a Payment Facilitator?.

The payments revenue inside a vertical SaaS business is rarely zero. It is almost always larger than the founder assumes. The work is making it visible and then choosing whether to capture it deliberately or leave it on the table.

Embedded payments is one of the few revenue lines that scales with merchant success without proportional sales effort. Modeling it correctly is the first step. The mechanics of how it shows up in your P&L, and what it does to your valuation, are covered in How to Read a Payments P&L and Payments Revenue SaaS Valuation.

The Margin Multiplier models your specific platform across all four arrangements in about 60 seconds. Start there if you want the platform-specific version of the numbers above. For the strategic conversation about what to do with those numbers at your platform, see the advisory engagement.