The decision that looks technical but isn't
When a SaaS company chooses its embedded payments program model — BaaS, PayFac, or direct bank — the conversation is usually framed as an infrastructure decision. Which vendor has the best API? Which BaaS provider onboards fastest? Which processor has the lowest transaction fees?
These are the wrong questions. The program model choice is a business model decision that determines the company's revenue quality, margin profile, customer retention economics, and ultimately its valuation multiple. The infrastructure conversation is how the decision gets implemented. The business model conversation is what the decision actually determines.
How the same payment volume produces different enterprise values
Two vertical SaaS companies. Both process $8M monthly in payment volume through their platforms. Both have 2,000 customers and $12M in ARR. Their enterprise values differ by $15M–$25M — not because of their SaaS metrics, but because of their payment program structure.
Company A processes payment volume on Stripe with zero payment revenue. The platform is a SaaS business with payment capability. Investors value it at 8x ARR: $96M.
Company B processes the same volume on a direct bank program generating 95 basis points net take rate — $912K in annual payment revenue at near-100% gross margin. The platform is a SaaS business with an embedded payments revenue stream. Investors value it at 11x blended revenue ($12M ARR + $912K payment revenue): $141M.
The enterprise value difference — $45M — comes from a program design decision made before the first vendor conversation. Not from additional customers, not from product features, not from sales execution. From the architecture of the payment program.
Why payment revenue is valued differently
Transaction revenue from embedded payments carries valuation characteristics that pure SaaS subscription revenue doesn't. It scales with customer transaction volume rather than seat count — meaning it grows without requiring additional sales. It is tied to workflow behavior (customers processing payments through the platform are more embedded than customers who only use the core SaaS product), which signals lower churn. And it is high-margin — captured interchange and float yield have near-zero incremental cost of revenue.
Investors pay a multiple on revenue quality, not just revenue quantity. Transaction revenue that grows with customer activity, has high margin, and signals workflow lock-in commands a higher multiple than subscription revenue with standard SaaS churn dynamics. The valuation premium is not always dramatic — but at meaningful payment volume, it is real and measurable.
The four architecture decisions that affect enterprise value most directly
Program model. BaaS captures 40–90 basis points. Direct bank captures 130–160 basis points. At $8M monthly, the annual economics difference is $480K–$864K. At a 12x revenue multiple, that economics gap represents $5.8M–$10.4M of enterprise value difference — from the same payment volume.
BIN selection. Consumer BINs generate 100–130 basis points. Commercial purchasing card BINs generate 175–250 basis points on eligible B2B transactions. The BIN is selected at program launch and is architecturally expensive to change. Programs that select consumer BINs when commercial BINs are available leave 45–120 basis points of interchange on every qualifying transaction — permanently, unless they rebuild.
Fee structure. Programs launched without a designed fee structure generate zero fee revenue — even when the products (same-day ACH, premium rail delivery, enhanced remittance) that justify fees are available. Retroactive fee introduction after customer relationships are established faces customer resistance that pre-designed fee structures don't. The fee structure decision at launch determines the fee revenue line at scale.
Float economics. BaaS programs retain float yield by default. Direct bank agreements make float yield a negotiable term. At $5M average daily FBO balance, 4.5% annualized yield is $225K per year — a revenue line that either exists or doesn't based on whether it was negotiated in the bank agreement. Missed float yield at a 12x multiple represents $2.7M of enterprise value that the bank is capturing instead of the platform.
What this means for the timing of architecture decisions
Every month a program runs on an architecture that doesn't support its optimal economics is a month of enterprise value being left on the table. The architecture decisions are most consequential before launch — when they can be made deliberately — and most expensive to change after launch, when they require re-architecture, bank renegotiation, and customer communication.
The investor who asks "what is your embedded finance strategy?" is asking a business model question, not a technology question. The answer that demonstrates enterprise value awareness — defined program model, economics at scale, migration path, bank relationship strategy — is the answer that changes the valuation conversation.
Want to understand the enterprise value implications of your current payment program architecture? Build the business case, or talk with us directly.