Frame

Blog

/

The 4 Stages of a SaaS Payments Journey: Which One Are You Stuck In?

You embedded payments. You told your board it was a new revenue line. You watched the first few merchants sign up and thought: this is going to work.

Then adoption flatlined at 18%.

The payments revenue is real, but it’s not what the model said it would be. Your support team is fielding reconciliation questions they don’t know how to answer. Somewhere in a contract you signed eighteen months ago, there’s language you didn’t fully understand at the time and haven’t revisited since. And the payments provider who was so attentive during the sales process has gone mostly quiet.

Nobody told you this part. Not the payments provider, not the fintech press, not the founder who gave you the warm intro. Everyone talked about the upside. Nobody explained the journey.

We learned this the hard way. At our previous company, we chose the wrong payments model and started as a gateway-only business when we should have been a facilitator. Then a risk hold froze our funds and we nearly lost the company. We’d processed one in four live event payments in North America by that point, and we still didn’t fully understand the contract we were operating under.

We built Forward because nobody should have to learn payments by almost going under.

Here’s what the journey actually looks like.

Stage 1: You Just Flipped the Switch

You’ve embedded payments. Merchants can accept cards through your platform. Something is technically working.

But “technically working” and “generating real revenue” are very different places, and right now you’re in the first one hoping it leads to the second.

Your adoption rate is probably somewhere under 20%. Maybe under 10%. You assumed merchants would sign up once the feature existed. The ones who did were early adopters. Curious, motivated, already sold on the idea. The rest of your base hasn’t moved.

This is the part nobody tells you: payments don’t sell themselves. It never has. The merchants on your platform are already paying someone else to process cards. Switching means paperwork, a new login, an explanation to their accountant, and a conversation with their bookkeeper about why the deposits look different now. That friction doesn’t disappear because you built a good product.

Meanwhile, you’re not entirely sure what you’re earning. The revenue share agreement made sense when your rep walked you through it. Now that you’re actually operating under it, some of the math feels off but you can’t quite identify where.

This is Stage 1. The foundation is in place. The hard work hasn’t started.

What’s actually at stake here: Every month you stay at 18% adoption is a month where the majority of your customers are paying a competitor to process payments that could be flowing through your platform. That gap doesn’t close on its own.

Stage 2: The Contract You Didn’t Fully Read

Volume is growing. Payments revenue is on the P&L and people are paying attention to it. You’ve maybe hired your first payments-focused person, or handed the function to someone in operations who’s figuring it out as they go.

And then something happens that makes you go back and read the contract.

Maybe it’s a risk hold, where a merchant’s funds were frozen, no explanation, your support team with nothing to tell them. Maybe it’s a chargeback that doesn’t resolve the way you expected. Maybe it’s your CFO asking why the effective rate is higher than what was quoted, and you can’t answer with precision.

You read the contract slowly this time.

Here’s what the payments industry has known for years and counted on you not knowing: payments contracts are written to be unreadable on purpose. The fee structure is split across multiple exhibit documents. The revenue share table has footnotes that modify the headline number. The termination clause has a non-solicit (lock-in). There’s a provision about network fee pass-throughs that can move your effective rate significantly depending on your card mix, and card mix is something that changes as your merchant base evolves, which means the rate you were quoted in year one may not be the rate you’re running in year two. 

None of this is accidental. Opacity is a feature of the industry, not a bug. The harder it is for you to understand your deal, the harder it is for you to know when to leave, and the more leverage your provider has at renewal. Could add something here about nomenclature and then link to our glossary as well… like the industry has its own language.

Stage 2 is where platforms discover this. Some figure it out early and renegotiate. Others don’t realize it until the contract comes up for renewal and suddenly the terms they thought were standard turn out to have been well below market.

What’s actually at stake here: You probably cannot tell, right now, whether your current payments deal is good. Not without an apples-to-apples comparison against what else is available to you. Most platforms can’t. That’s not a failure of diligence. It’s the expected outcome of a system designed to prevent you from knowing.

Stage 3: You’re Growing. So Is the Complexity.

Volume is real now, typically $50M or more annually. You have a meaningful base of merchants on payments. The revenue line is one of the better stories in your board deck.

And the operational weight has compounded.

Your card mix has shifted as you’ve grown, and it’s affecting your effective rate in ways you don’t have clean visibility into. Certain merchant segments have higher risk profiles than others, and your risk model isn’t calibrated specifically to your industry. Reconciliation is still partially manual, and the merchants who struggle with it are your most vocal support tickets. Interchange costs are your single largest expense and you’re not actively managing them.

Adoption is still the biggest lever and it’s still stuck. Even platforms doing well at this stage are typically running below a 70% attach rate. That sounds like a rounding error until you do the math: moving from 40% to 70% adoption on a base of 500 customers, at $600K in annual payment volume each, means roughly $1.8M in incremental revenue at a 1% net take rate. It’s not a rounding error. It’s probably your next hire, or your next product, or the margin that makes your next raise easier.

But you haven’t built the motion to move that number. Payments adoption doesn’t respond to email campaigns or in-app prompts the way your SaaS features do. It requires merchant education, targeted outreach, dedicated reps who understand both the product and the specific objections merchants have about switching. Most platforms haven’t built that. They’ve tried to solve a sales problem with a product solution.

What’s actually at stake here: The platforms that exit Stage 3 cleanly are the ones that treat adoption like a growth function with dedicated people, dedicated process, and a willingness to sell. The ones that stall treat it like a product metric they can A/B test their way out of.

Stage 4: You’re Ready to Own It

Volume is significant, often $10B or more annually. Adoption is above 50% and climbing. You have a payments team and internal operational capabilities. The question is no longer whether payments is working. It’s how much of what it generates you should be keeping.

Registering as a Payment Facilitator and taking compliance, risk, and operations fully in-house is the move that lets you retain the full economics. Instead of sharing revenue with a provider, you use them as a technology platform and pay a SaaS fee. Multiple platforms have already made this transition. The ones who do it right keep the same tech stack they’ve been building on. They don’t start over.

The ones who do it wrong move too fast and discover that compliance and risk are more operationally complex than they anticipated. Or they wait too long, locking in a provider relationship well past the point where the economics justify it.

The decision to register as a PFAC should be driven by volume, team capacity, and operational readiness, not ambition or momentum. Getting the timing right matters more than getting there fast.

What’s actually at stake here: Done right, Stage 4 is the most profitable position in the vertical software stack. Done wrong, it’s the most expensive mistake a payments-enabled platform can make.

Where Are You?

Most platforms we talk to are somewhere between Stage 1 and Stage 3. Many have been at Stage 2 longer than they know, operating under a deal that made sense when they signed it and hasn’t been pressure-tested since.

The fastest way to find out where you stand isn’t a conversation. It’s a comparison. Put your current deal next to what the market actually offers, line by line. Most platforms are surprised by what they find.

See how your deal compares.

Subscribe to Forward

Share article

Build payments 
into your product

Want to learn more or apply this specifically to your business? Speak to a payments expert today.

clouds fill