Taking payments vs.
building a payments business
Five questions to answer honestly about your program
You launched a payments product. Your merchants can now accept payments. You’ve checked the box. But there’s a wide gap between a checked box and a real payments business — and the difference is worth millions.
Most SaaS platforms have payments. Very few have a payments business. The distinction isn’t about the technology — it’s about how payments is positioned, resourced, and operated inside your company.
The platforms that treat payments as a revenue line build a compounding growth engine. The ones that treat it as a feature check a box and wonder why the number never moves. Here are five questions that tell you which one you have.
Five questions to answer honestly about your payments program
Each question below maps to a specific operational gap. Most platforms fail at least three of them. The ones that pass all five are the ones compounding.
When someone asks “Do you have payments?” — does your answer describe a real revenue business, or just a processing feature?
This is the gut check. The answer most platforms give sounds like: “Yes, we integrated Stripe,” or “Yes, merchants can process through us.” That answer means payments exists. It does not mean you have a payments business.
A strong answer sounds different. It sounds like: “Yes — we generate a dollar of payments revenue for every dollar of software revenue.” That answer describes an outcome. It describes a business line, not a capability.
The distinction matters because integration-based answers reflect a feature someone built. Revenue-based answers reflect a business someone runs. If your answer is integration-based, the remaining four questions will tell you exactly why.
For every dollar of SaaS revenue, how many dollars of embedded finance revenue do you generate?
This is the proof behind Question 1. If you have a real payments business, payments should show up as a meaningful revenue line — not just a capability on your pricing page. The benchmark that separates platforms with a real payments business from those that don’t: greater than 1:1 embedded finance revenue to SaaS revenue.
ServiceTitan, Toast, Mindbody — the platforms that have built genuine embedded finance businesses show this in their public filings. Payments revenue approaches or exceeds software revenue. That’s not a coincidence. It’s the result of treating payments as a business line with its own strategy, ownership, and operating rhythm.
Most platforms are nowhere near 1:1. That gap is the opportunity. The remaining questions explain exactly where it’s going.
What percentage of your merchants are actually using your payments product?
Attach rate is the single most important operational metric in embedded payments, and most platforms either don’t track it or don’t like what they see when they do. The industry average is below 20%. Forward partners average 70%. That gap is not a product gap — it’s a strategy gap.
Every unattached merchant is a merchant whose payment volume — and the revenue share that comes with it — is going somewhere else. If fewer than half your merchants are processing through your payments product, you have a feature your customers are ignoring, not a business they’re depending on.
5,000
$20K
20%
Is payments your product — or are you just referring your customers to someone else’s?
There’s a meaningful difference between a white-labeled payments offering and a referral relationship with a payments vendor. In a white-label model, your merchants see your brand, your portal, your pricing, and your support. The experience is yours. In a referral model, you’re pointing customers to a third party and collecting a small check for the privilege.
Referral relationships feel easy at launch and require almost no investment. They also deliver almost no return — and they hand your customers’ payment relationships to someone who has no obligation to keep them inside your ecosystem.
If your merchants log into a portal that doesn’t have your name on it to manage their payments, you’re not in the payments business. You’re in the referral business.
When your merchants have a problem, do they feel like they’re being thrown over a fence?
This is the question most platforms never ask until they’ve already lost merchants over it. When a merchant has a chargeback, a funding delay, or a question about their rate — who do they talk to? If the answer involves contacting a third-party vendor directly, you’ve handed off the relationship at the most critical moment.
Payments problems are emotionally charged. A merchant who can’t get their money on time is a merchant at churn risk — from your software, not just from your payments product. Getting help should feel like one platform, not a handoff between two companies.
White-labeled payments infrastructure keeps the relationship yours. The merchant calls your support. Your team has the visibility and the tools to answer. The payments vendor is invisible.
Built for platforms that want payments to compound — not just exist.
Full white-label infrastructure. Above buy-rate economics. Full legal and technical portability. A clear path to registered PayFac status. And a team that works directly alongside yours on program design, merchant activation, and ongoing optimization.
Not just an API. A payments partnership.
